Is CVE-2026-44585 exploited in the wild?

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

How severe is CVE-2026-44585?

Medium severity, with a CVSS score of 5.4, published 20 July 2026.

Which products and versions are affected?

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

Is there a fix for CVE-2026-44585?

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

How is CVE-2026-44585 attacked?

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

Am I affected by CVE-2026-44585?

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-2026-44585: Paymenter authorization bypass in ticket creation endpoint

Q: Is there a fix for CVE-2026-44585?

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

Q: How is CVE-2026-44585 attacked?

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

Q: Am I affected by CVE-2026-44585?

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-2026-44585 · Severity: medium · CVSS 5.4 · Published 2026-07-20

Paymenter, an open-source platform for managing hosting services and webshops, contains a security flaw in its support ticket system. Logged-in users can create support tickets that incorrectly reference services belonging to other customers by manually changing a service ID number. While this does not grant direct access to private data, it could lead to confusion, privacy leaks when support staff review the ticket, or unauthorized service inquiries.

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

Quick answers

Is CVE-2026-44585 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-44585 being exploited in the wild.
How severe is CVE-2026-44585?: Medium severity, with a CVSS score of 5.4, published 20 July 2026.
Which products and versions are affected?: paymenter/paymenter (Packagist) < 1.5.0, ECOSYSTEM:introduced=0,fixed=1.5.0; Paymenter < 1.5.0.
Is there a fix for CVE-2026-44585?: Yes. paymenter/paymenter (Packagist): upgrade to 1.5.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-44585 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-44585?: 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.5.0 or later
```
composer require paymenter/paymenter:^1.5.0
```

Technical details

The vulnerability is classified as an Insecure Direct Object Reference (IDOR) or Broken Object Level Authorization (BOLA) within the ticket creation endpoint. The root cause is a failure to enforce ownership validation on the user-supplied service identifier during the ticket submission process. An authenticated attacker can intercept and modify the service ID in the request to associate a new ticket with a third-party service. While this does not allow direct data exfiltration or service modification, it permits unauthorized referencing of objects, potentially exposing service metadata to support personnel. This issue is tracked as CWE-639 and CWE-862 and is resolved in version 1.5.0.

Affected products

Paymenter Paymenter < 1.5.0

Identifiers

CVE-2026-44585
GHSA-x93q-x9pc-w5hw

Timeline

2026-06-10: advisory: GitHub Security Advisory published
2026-07-20: disclosed: NVD publication date

References

https://github.com/Paymenter/Paymenter/security/advisories/GHSA-x93q-x9pc-w5hw

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