Skip to content
Fencer Intel
critical 9.8

CVE-2019-14537 json

Access of Resource Using Incompatible Type ('Type Confusion') in yourls/yourls

published 7y ago modified last mo. also GHSA-vf23-f26f-mjj9 , EUVD-2019-0679

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
6.1%
EPSS 6.1% chance of exploitation in 30 days, percentile 93%
public exploits
0
none known

Summary

YOURLS through 1.7.3 is affected by a type juggling vulnerability in the api component that can result in login bypass.

Patch / fix

  • packagist yourls/yourls 1.7.4

Is CVE-2019-14537 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2019-14537 updated cvss 7.3

yourls: juggling vulnerability in api component leads tp login bypass

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

6.15% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/Wocanilo/CVE-2019-14537 referenced PoC, tagged "exploit" by a source, unverified
  • security-garage.com https://security-garage.com/index.php/cves/cve-2019-14537-api-authentication-bypass-via-type-juggling referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
packagist yourls/yourls
<1.7.4
1.7.4

Classification

Weakness
  • CWE-843 Access of Resource Using Incompatible Type

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.