Is CVE-2025-58048 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2025-58048 being exploited in the wild.

How severe is CVE-2025-58048?

Critical severity, with a CVSS score of 9.9, published 22 June 2026.

Which products and versions are affected?

paymenter/paymenter (Packagist) < 1.2.11, ECOSYSTEM:introduced=0,fixed=1.2.11; Paymenter < 1.2.11.

Is there a fix for CVE-2025-58048?

Yes. paymenter/paymenter (Packagist): upgrade to 1.2.11 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2025-58048 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2025-58048?

Check whether you run paymenter/paymenter (Packagist) or Paymenter at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2025-58048: Paymenter RCE via unrestricted file upload in ticket attachments

Q: Is there a fix for CVE-2025-58048?

Yes. paymenter/paymenter (Packagist): upgrade to 1.2.11 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2025-58048 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2025-58048?

Check whether you run paymenter/paymenter (Packagist) or Paymenter at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2025-58048 · Severity: critical · CVSS 9.9 · Published 2026-06-22

Paymenter, an open-source platform for hosting providers to manage billing and clients, contains a critical flaw in its support ticket system. An authenticated user can upload malicious files that allow them to take full control of the server. This could lead to the theft of customer data, exposure of sensitive configuration files, and complete service disruption.

Technologies: paymenter/paymenter (Packagist), Paymenter. Vendors: Packagist, Paymenter.

Quick answers

Is CVE-2025-58048 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-58048 being exploited in the wild.
How severe is CVE-2025-58048?: Critical severity, with a CVSS score of 9.9, published 22 June 2026.
Which products and versions are affected?: paymenter/paymenter (Packagist) < 1.2.11, ECOSYSTEM:introduced=0,fixed=1.2.11; Paymenter < 1.2.11.
Is there a fix for CVE-2025-58048?: Yes. paymenter/paymenter (Packagist): upgrade to 1.2.11 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2025-58048 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2025-58048?: Check whether you run paymenter/paymenter (Packagist) or Paymenter at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

paymenter/paymenter (Packagist): upgrade to 1.2.11 or later
```
composer require paymenter/paymenter:^1.2.11
```

Technical details

An unrestricted file upload vulnerability (CWE-434) exists in the ticket attachments functionality of Paymenter. A malicious authenticated user with low privileges can upload arbitrary files, such as PHP scripts, to the server. Because these files are stored in a web-accessible directory without sufficient execution restrictions, an attacker can execute arbitrary system commands under the context of the web server user. This allows for full application and server compromise, including database extraction and credential theft. The issue is resolved in version 1.2.11.

Affected products

Paymenter Paymenter < 1.2.11

Identifiers

CVE-2025-58048
GHSA-5pm9-r2m8-rcmj

Timeline

2025-08-28: disclosed
2025-08-28: patched: Released in v1.2.11
2026-06-22: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.