Skip to content

Paymenter vulnerable to Remote Code Execution via public file uploads

Critical severity GitHub Reviewed Published Aug 28, 2025 in Paymenter/Paymenter • Updated Jun 22, 2026

Package

composer paymenter/paymenter (Composer)

Affected versions

< 1.2.11

Patched versions

1.2.11

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 Paymenter/Paymenter@87c3db4 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.

References

@CorwinDev CorwinDev published to Paymenter/Paymenter Aug 28, 2025
Published by the National Vulnerability Database Aug 28, 2025
Published to the GitHub Advisory Database Jun 22, 2026
Reviewed Jun 22, 2026
Last updated Jun 22, 2026

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(30th percentile)

Weaknesses

Unrestricted Upload of File with Dangerous Type

The product allows the upload or transfer of dangerous file types that are automatically processed within its environment. Learn more on MITRE.

CVE ID

CVE-2025-58048

GHSA ID

GHSA-5pm9-r2m8-rcmj

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.