CVE-2025-58048 is a critical-severity unrestricted upload of dangerous file types vulnerability in paymenter/paymenter (composer), affecting versions < 1.2.11. It is fixed in 1.2.11.
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: 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.
The application accepts file uploads without adequately restricting the file type or content. Typical impact: remote code execution if the uploaded file can be served and executed on the server.
CVE-2025-58048 has a CVSS score of 9.9 (Critical). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.
A fixed version is available (1.2.11). Upgrading removes the vulnerable code path.
composer
paymenter/paymenter (< 1.2.11)paymenter/paymenter → 1.2.11 (composer)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.
Kodem's runtime-powered SCA identifies whether CVE-2025-58048 is reachable in your applications. Explore open-source security for your team.
See if CVE-2025-58048 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2025-58048 in your environment →Upgrade paymenter/paymenter to 1.2.11 or later to resolve this vulnerability.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2025-58048 is a critical-severity unrestricted upload of dangerous file types vulnerability in paymenter/paymenter (composer), affecting versions < 1.2.11. It is fixed in 1.2.11. The application accepts file uploads without adequately restricting the file type or content.
CVE-2025-58048 has a CVSS score of 9.9 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
paymenter/paymenter (composer) versions < 1.2.11 is affected.
Yes. CVE-2025-58048 is fixed in 1.2.11. Upgrade to this version or later.
Whether CVE-2025-58048 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
Upgrade paymenter/paymenter to 1.2.11 or later.