GHSA-47mc-qmh2-mqj4 is a medium-severity (CVSS 6.8) Unrestricted File Upload vulnerability in automad/automad. A fix is available for automad/automad — see the affected versions and patch details below.
Automad arbitrary file upload vulnerability
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for GHSA-47mc-qmh2-mqj4.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-47mc-qmh2-mqj4 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
automad/automadReal-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
An arbitrary file upload vulnerability in the image upload function of Automad v2.0.0 allows attackers to execute arbitrary code via a crafted file.
The malicious file has to be prepared and uploaded manually by the admin. Usually there is only one admin per site and that is the owner.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | automad/automad | all versions | 2.0.0-alpha.5composer require automad/automad:^2.0.0-alpha.5 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for automad/automad, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update automad/automad to 2.0.0-alpha.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-47mc-qmh2-mqj4 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-47mc-qmh2-mqj4 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-47mc-qmh2-mqj4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-47mc-qmh2-mqj4 in your dependencies?
O3 Security finds GHSA-47mc-qmh2-mqj4 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.