GHSA-5pm9-r2m8-rcmj is a critical-severity (CVSS 9.9) Unrestricted File Upload vulnerability in paymenter/paymenter. O3 Security confirms whether GHSA-5pm9-r2m8-rcmj is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Paymenter vulnerable to Remote Code Execution via public file uploads
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-5pm9-r2m8-rcmj.
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-5pm9-r2m8-rcmj 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 369,023 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
paymenter/paymenterReal-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
Impact
The ticket attachments functionality in Paymenter allows a malicious authenticated user to upload arbitrary files.
With the ability to execute arbitrary code, this vulnerability can be exploited in numerous ways, including but not limited to:
- Extracting sensitive data from the database (e.g. customer information).
- Reading credentials from .env or other configuration files.
- Running arbitrary system commands under the web server user context.
This issue is Critical as it allows a low-privilege authenticated user to fully compromise the application and underlying server.
Patches
This vulnerability was patched by https://github.com/Paymenter/Paymenter/commit/87c3db42282ada1e3cda54b9a01f846926c0669b and was released under the v1.2.11 tag without any other code modifications compared to v1.2.10.
Work arounds
If upgrading is not immediately possible, administrators can mitigate this vulnerability with one or more of the following measures:
- Updating nginx config to download attachments instead of executing them:
location ^~ /storage/ {
types { }
default_type application/octet-stream;
add_header X-Content-Type-Options nosniff;
try_files $uri =404;
}
- Disallow access to /storage/ fully using a WAF such as Cloudflare
These workarounds significantly reduce risk, but the only guaranteed resolution is upgrading to v1.2.11 or later.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | paymenter/paymenter | all versions | 1.2.11 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for paymenter/paymenter. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update paymenter/paymenter to 1.2.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5pm9-r2m8-rcmj 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 pinpoints whether GHSA-5pm9-r2m8-rcmj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-5pm9-r2m8-rcmj. 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-5pm9-r2m8-rcmj in your dependencies?
O3 detects GHSA-5pm9-r2m8-rcmj across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.