Podinfo affected by Arbitrary File Upload that leads to Stored Cross-Site Scripting (XSS)GHSA-mw8w-q3f7-2v85
MEDIUMFix: stefanprodan/podinfo#463GHSA-mw8w-q3f7-2v85 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in github.com/stefanprodan/podinfo. A fix is available for github.com/stefanprodan/podinfo — see the affected versions and patch details below.
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.
Exploitation and automatability from CISA’s SSVC triage for GHSA-mw8w-q3f7-2v85.
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
github.com/stefanprodan/podinfoReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Arbitrary File Upload in podinfo thru 6.9.0 allows unauthenticated attackers to upload arbitrary files via crafted POST request to the /store endpoint. The application renders uploaded content without a restrictive Content-Security-Policy (CSP) or adequate Content-Type validation, leading to Stored Cross-Site Scripting (XSS).
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/stefanprodan/podinfo | all versions | 1.8.1-0.20260314125853-83deb7fcb742go get github.com/stefanprodan/podinfo@v1.8.1-0.20260314125853-83deb7fcb742 |
Affected Products
podinfostefanprodanDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/stefanprodan/podinfo, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/stefanprodan/podinfo to 1.8.1-0.20260314125853-83deb7fcb742 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mw8w-q3f7-2v85 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-mw8w-q3f7-2v85 in your dependencies?
Find it across Go, including transitive dependencies.