invoiceninja is vulnerable to Cross-site ScriptingGHSA-xg6r-5gx4-qxjm
MEDIUMFix: invoiceninja/invoiceninja@1186eaaGHSA-xg6r-5gx4-qxjm is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in hillelcoren/invoice-ninja. 1 public exploit reference exists, so weaponization risk is real. A fix is available for hillelcoren/invoice-ninja — 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
GHSA-xg6r-5gx4-qxjm by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
hillelcoren/invoice-ninjaReal-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
invoiceninja is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | hillelcoren/invoice-ninja | all versions | 5.3.35composer require hillelcoren/invoice-ninja:^5.3.35 |
Affected Products
invoice ninjainvoiceninjaResearch 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 hillelcoren/invoice-ninja, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update hillelcoren/invoice-ninja to 5.3.35 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xg6r-5gx4-qxjm 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 GHSA-xg6r-5gx4-qxjm in your dependencies?
Find it across Packagist, including transitive dependencies.