CVE-2022-0472 is a high-severity (CVSS 8.1) Unrestricted File Upload vulnerability in jsdecena/laracom. 1 public exploit reference exists, so weaponization risk is real. A fix is available for jsdecena/laracom — see the affected versions and patch details below.
Unrestricted Upload of File with Dangerous Type in jsdecena/laracom
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2022-0472 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
jsdecena/laracomReal-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
jsdecena/laracom prior to version 2.0.9 is vulnerable to Unrestricted Upload of File with Dangerous Type.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | jsdecena/laracom | all versions | 2.0.9composer require jsdecena/laracom:^2.0.9 |
Affected Products
laracomlaracom_projectResearch 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 jsdecena/laracom, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update jsdecena/laracom to 2.0.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-0472 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-2022-0472 in your dependencies?
Find it across Packagist, including transitive dependencies.