CVE-2021-40926 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in james-heinrich/getid3. 1 public exploit reference exists, so weaponization risk is real. A fix is available for james-heinrich/getid3 — see the affected versions and patch details below.
Cross-site scripting in demos/demo.mysqli.php in getID3
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2021-40926 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
james-heinrich/getid3Real-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
Cross-site scripting (XSS) vulnerability in demos/demo.mysqli.php in getID3 1.X and v2.0.0-beta allows remote attackers to inject arbitrary web script or HTML via the showtagfiles parameter.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | james-heinrich/getid3 | ≥ 1.0.0&&< 1.9.21 | 1.9.21composer require james-heinrich/getid3:^1.9.21 |
Affected Products
getid3getid3Research 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 james-heinrich/getid3, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update james-heinrich/getid3 to 1.9.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-40926 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2021-40926 in your dependencies?
Find it across Packagist, including transitive dependencies.