Access of Resource Using Incompatible Type ('Type Confusion') in yourls/yourlsGHSA-vf23-f26f-mjj9
CRITICALFix: YOURLS/YOURLS#2542GHSA-vf23-f26f-mjj9 is a critical-severity (CVSS 9.8) CWE-843 vulnerability in yourls/yourls. 4 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for yourls/yourls — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
yourls/yourlsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Impact
YOURLS through 1.7.3 is affected by a type juggling vulnerability in the API component that can result in login bypass.
Patches
https://github.com/YOURLS/YOURLS/releases/tag/1.7.4 https://github.com/YOURLS/YOURLS/pull/2542
References
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14537
- https://github.com/Wocanilo/CVE-2019-14537
For more information
If you have any questions or comments about this advisory:
- Open an issue in YOURLS repository
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | yourls/yourls | all versions | 1.7.4composer require yourls/yourls:^1.7.4 |
Affected Products
yourlsyourlsResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for yourls/yourls, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update yourls/yourls to 1.7.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vf23-f26f-mjj9 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is GHSA-vf23-f26f-mjj9 in your dependencies?
Find it across Packagist, including transitive dependencies.