CVE-2026-44585

MEDIUMPre-NVD 5.45.4—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 92% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.4Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Paymenter is a free and open-source webshop solution for management of hosting services. In versions prior to 1.5.0, the ticket creation endpoint accepts a user-supplied service identifier without enforcing ownership validation, allowing authenticated users to create support tickets referencing services belonging to other accounts by modifying the service ID in the request. An attacker could modify the service ID value in the client-side request and successfully create a ticket associated with another user's service. The vulnerability requires authentication and does not provide direct access to service contents or customer data. However, referenced service information could become visible to support personnel handling the ticket. Successful exploitation could allow an authenticated user to: create support tickets referencing services belonging to other users, potentially cause support staff to interact with or review unrelated customer services. The vulnerability did not allow direct access to another user's service, modification of another user's service or retrieval of confidential service data through the vulnerable endpoint itself. This issue has been fixed in version 1.5.0.

CVSS v3
5.4
EG Score
5.4(medium)
EG Risk
24(Track)
EG Risk 24/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity54% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
21%
KEV
Not listed

Published

June 22, 2026

Last Modified

July 23, 2026

Advisory Details (1)

Auto-updated Jul 20, 2026
Patch available. Sources: github.
github Patch Available

Broken object level authorization via service reference manipulation on ticket creation · Advisory · Paymenter/Paymenter · GitHub

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

Vendor Advisories for CVE-2026-44585(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFixed inDependents
paymenter/paymenter0.1 ... v1.1.1 (32 versions)1.5.0—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 46× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-27 14:25 UTCEPSS rescore
  2. 2026-08-26 14:46 UTCEPSS rescore
  3. 2026-08-25 13:49 UTCEPSS rescore
  4. 2026-08-24 13:55 UTCEG score recompute
  5. 2026-08-22 15:07 UTCEG score recompute
  6. 2026-08-21 23:49 UTCEPSS rescore
  7. 2026-08-20 07:50 UTCEG score recompute
  8. 2026-08-19 17:04 UTCEPSS rescore
  9. 2026-08-19 04:51 UTCEG score recompute
  10. 2026-08-18 13:48 UTCEPSS rescore
  11. 2026-08-17 13:47 UTCEPSS rescore
  12. 2026-08-17 09:26 UTCEG score recompute
  13. 2026-08-16 14:56 UTCEPSS rescore
  14. 2026-08-16 10:37 UTCEG score recompute
  15. 2026-08-16 02:14 UTCEPSS rescore
  16. 2026-08-15 11:49 UTCEG score recompute
  17. 2026-08-15 01:30 UTCEPSS rescore
  18. 2026-08-14 12:59 UTCEG score recompute
  19. 2026-08-13 22:00 UTCEPSS rescore
  20. 2026-08-12 15:04 UTCEG score recompute
  21. 2026-08-12 13:51 UTCEPSS rescore
  22. 2026-08-11 16:14 UTCEG score recompute
  23. 2026-08-11 00:00 UTCEPSS rescore
  24. 2026-08-09 17:48 UTCEG score recompute
  25. 2026-08-09 13:46 UTCEPSS rescore
Show 35 more
  1. 2026-08-08 19:00 UTCEG score recompute
  2. 2026-08-08 16:37 UTCEPSS rescore
  3. 2026-08-07 20:11 UTCEG score recompute
  4. 2026-08-06 21:22 UTCEG score recompute
  5. 2026-08-06 13:46 UTCEPSS rescore
  6. 2026-08-05 22:33 UTCEG score recompute
  7. 2026-08-05 19:17 UTCEPSS rescore
  8. 2026-08-04 23:44 UTCEG score recompute
  9. 2026-08-04 15:10 UTCEPSS rescore
  10. 2026-08-04 10:38 UTCEPSS rescore
  11. 2026-08-04 00:56 UTCEG score recompute
  12. 2026-08-03 10:36 UTCEPSS rescore
  13. 2026-08-02 03:18 UTCEG score recompute
  14. 2026-08-02 02:27 UTCEPSS rescore
  15. 2026-08-01 04:29 UTCEG score recompute
  16. 2026-08-01 04:16 UTCEPSS rescore
  17. 2026-07-31 03:42 UTCEG score recompute
  18. 2026-07-30 16:28 UTCEPSS rescore
  19. 2026-07-30 02:42 UTCEG score recompute
  20. 2026-07-30 01:30 UTCEPSS rescore
  21. 2026-07-29 01:56 UTCEG score recompute
  22. 2026-07-28 15:36 UTCEPSS rescore
  23. 2026-07-28 03:02 UTCEG score recompute
  24. 2026-07-27 14:13 UTCEPSS rescore
  25. 2026-07-27 04:13 UTCEG score recompute
  26. 2026-07-26 14:54 UTCEPSS rescore
  27. 2026-07-26 14:54 UTCEPSS rescore
  28. 2026-07-26 05:13 UTCEG score recompute
  29. 2026-07-25 14:18 UTCEPSS rescore
  30. 2026-07-24 14:17 UTCEPSS rescore
  31. 2026-07-23 14:18 UTCEPSS rescore
  32. 2026-07-23 03:15 UTCEG score recompute
  33. 2026-07-22 14:08 UTCEPSS rescore
  34. 2026-07-21 15:24 UTCEPSS rescore
  35. 2026-06-22 20:36 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-44585?
CVE-2026-44585 is a medium vulnerability published on June 22, 2026. Paymenter is a free and open-source webshop solution for management of hosting services. In versions prior to 1.5.0, the ticket creation endpoint accepts a user-supplied service identifier without enforcing ownership validation, allowing authenticated users to create support tickets referencing…
When was CVE-2026-44585 disclosed?
CVE-2026-44585 was first published in the National Vulnerability Database on June 22, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44585 actively exploited?
CVE-2026-44585 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 79.5% of all scored CVEs.
What is the CVSS score of CVE-2026-44585?
CVE-2026-44585 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-44585?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44585, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-44585

Explore →

Is Your Infrastructure Affected by CVE-2026-44585?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs