Cross site scripting in FacturaScriptsGHSA-p3w3-4ppm-c3f6
CRITICALFix: neorazorx/facturascripts@aa9f28cGHSA-p3w3-4ppm-c3f6 is a critical-severity (CVSS 9) Cross-site Scripting (XSS) vulnerability in facturascripts/facturascripts. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for facturascripts/facturascripts — 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
facturascripts/facturascriptsReal-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
Stored XSS via upload plugin functionality in zip format in GitHub repository neorazorx/facturascripts prior to 2022.06. Cross-site scripting attacks can have devastating consequences. Code injected into a vulnerable application can exfiltrate data or install malware on the user's machine. Attackers can masquerade as authorized users via session cookies, allowing them to perform any action allowed by the user account.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | facturascripts/facturascripts | all versions | 2022.06composer require facturascripts/facturascripts:^2022.06 |
Affected Products
facturascriptsfacturascriptsResearch 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 facturascripts/facturascripts, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update facturascripts/facturascripts to 2022.06 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p3w3-4ppm-c3f6 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-p3w3-4ppm-c3f6 in your dependencies?
Find it across Packagist, including transitive dependencies.