CVE-2026-44585

MEDIUMPre-NVD 5.45.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 5.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (19th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week
5.4EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.4MEDIUMmedium confidence
EG Risk
24
EG Risk 24/100

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 (value × EchelonGraph’s weight)
Severity54% × 45%
The EG Score, 5.4 of 10.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
19th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 22, 2026

Last Modified

July 23, 2026

Advisory Details (1)

Auto-updated Jul 20, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

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 rangeFix by version rangeDependents
paymenter/paymenter0.1 ... v1.1.1 (32 versions)
  • every version up to 1.5.0: fixed in 1.5.0
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 27× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats.

  1. 2026-10-11 19:47 UTCEG score recompute
  2. 2026-10-11 17:01 UTCEG score recompute
  3. 2026-10-11 14:27 UTCEG score recompute
  4. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  5. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  6. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  7. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  8. 2026-10-08 05:24 UTCOSV refresh
  9. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  10. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  11. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  12. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  13. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  14. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  15. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  16. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  17. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  18. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  19. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  20. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  21. 2026-09-18 11:14 UTCEG score recompute
  22. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  23. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  24. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  25. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 20th percentile
Show 74 more
  1. 2026-09-13 12:30 UTCEG score recompute
  2. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  3. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  4. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  5. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  6. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  7. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  8. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  9. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  10. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  11. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  12. 2026-08-30 20:32 UTCEG score recompute
  13. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  14. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  15. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  16. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  17. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  18. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  19. 2026-08-24 13:55 UTCEG score recompute
  20. 2026-08-22 15:07 UTCEG score recompute
  21. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  22. 2026-08-20 07:50 UTCEG score recompute
  23. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  24. 2026-08-19 04:51 UTCEG score recompute
  25. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  26. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  27. 2026-08-17 09:26 UTCEG score recompute
  28. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  29. 2026-08-16 10:37 UTCEG score recompute
  30. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  31. 2026-08-15 11:49 UTCEG score recompute
  32. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  33. 2026-08-14 12:59 UTCEG score recompute
  34. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  35. 2026-08-12 15:04 UTCEG score recompute
  36. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  37. 2026-08-11 16:14 UTCEG score recompute
  38. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  39. 2026-08-09 17:48 UTCEG score recompute
  40. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  41. 2026-08-08 19:00 UTCEG score recompute
  42. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  43. 2026-08-07 20:11 UTCEG score recompute
  44. 2026-08-06 21:22 UTCEG score recompute
  45. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  46. 2026-08-05 22:33 UTCEG score recompute
  47. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  48. 2026-08-04 23:44 UTCEG score recompute
  49. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  50. 2026-08-04 10:38 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  51. 2026-08-04 00:56 UTCEG score recompute
  52. 2026-08-03 10:36 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  53. 2026-08-02 03:18 UTCEG score recompute
  54. 2026-08-02 02:27 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  55. 2026-08-01 04:29 UTCEG score recompute
  56. 2026-08-01 04:16 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  57. 2026-07-31 03:42 UTCEG score recompute
  58. 2026-07-30 16:28 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  59. 2026-07-30 02:42 UTCEG score recompute
  60. 2026-07-30 01:30 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  61. 2026-07-29 01:56 UTCEG score recompute
  62. 2026-07-28 15:36 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  63. 2026-07-28 03:02 UTCEG score recompute
  64. 2026-07-27 14:13 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  65. 2026-07-27 04:13 UTCEG score recompute
  66. 2026-07-26 14:54 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  67. 2026-07-26 05:13 UTCEG score recompute
  68. 2026-07-25 14:18 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  69. 2026-07-24 14:17 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  70. 2026-07-23 14:18 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  71. 2026-07-23 03:15 UTCEG score recompute
  72. 2026-07-22 14:08 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  73. 2026-07-21 15:24 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  74. 2026-06-22 20:36 UTCEG score recompute

Related CVEs(same product + same CWE)· as of October 10, 2026

Frequently asked(5)

What is CVE-2026-44585?
CVE-2026-44585 is a medium-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-44585 published?
The CVE record for CVE-2026-44585 was published on June 22, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 23, 2026; the record at its source may have been updated since.
Is CVE-2026-44585 actively exploited?
CVE-2026-44585 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (19th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-44585?
CVE-2026-44585 has a CVSS base score of 5.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-44585?
A fix for CVE-2026-44585 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-44585 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs