CVE-2025-58048 is a critical-severity (CVSS 9.9) Unrestricted File Upload vulnerability in paymenter/paymenter. A fix is available for paymenter/paymenter — see the affected versions and patch details below.
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 CVE-2025-58048.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2025-58048 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 394,803 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
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.11composer require paymenter/paymenter:^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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update paymenter/paymenter to 1.2.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-58048 is resolved across your whole dependency graph.
Workarounds
Treat uploaded files as untrusted until proven otherwise: validate the actual content type rather than the supplied extension, store uploads outside the web root on a volume mounted without execute permission, and rename them to server-generated identifiers so an attacker cannot choose the path a request will later resolve.
Frequently Asked Questions
Is CVE-2025-58048 in your dependencies?
Find it across Packagist, including transitive dependencies.