CVE-2026-47198

HIGHPre-NVD 8.58.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (32nd 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
8.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.5Exploit: 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.1, the checkout component improperly filters URL-writable properties, allowing authenticated users to inject arbitrary key-value pairs into server provisioning parameters. Because bundled server extensions prioritize these user-supplied properties over administrator-defined configurations, a regular user can override hosting plans and resource limits at checkout without special privileges. The Checkout Livewire component's $checkoutConfig property exposed via URL query parameters, only validating keys explicitly defined by an extension's configuration method, allowing any undefined injected keys to bypass validation entirely. These unsanitized keys are then stored directly in the database by the cart component and later passed to server extensions during provisioning, enabling user-injected data to override intended administrator settings. Depending on the active extension, this leads to unauthorized overrides of core resource limits (such as CPU, RAM, storage, or package tiers). No administrative privileges are required to exploit this vulnerability. This issue has been fixed in version 1.5.1.

CVSS v3
8.5
EG Score
8.5HIGHmedium confidence
EG Risk
38
EG Risk 38/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)
Severity85% × 45%
The EG Score, 8.5 of 10.
Exploitation0.4% × 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.4%
EPSS %ILE
32nd
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 30, 2026

Last Modified

July 23, 2026

Advisory Details (1)

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

URL parameter injection bypasses paid plan limits at checkout · Advisory · Paymenter/Paymenter · GitHub

https://github.com/Paymenter/Paymenter/security/advisories/GHSA-5q4q-834j-g8g4

Vendor Advisories for CVE-2026-47198(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.1: fixed in 1.5.1
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 28× 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.

Showing the most recent 100 of 109 refreshes on record for this CVE.

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. None are among the latest 100 rows. The 9 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-47198?
CVE-2026-47198 is a high-severity vulnerability; its CVE record was published on June 30, 2026. Paymenter is a free and open-source webshop solution for management of hosting services. In versions prior to 1.5.1, the checkout component improperly filters URL-writable properties, allowing authenticated users to inject arbitrary key-value pairs into server provisioning parameters. Because…
When was the CVE record for CVE-2026-47198 published?
The CVE record for CVE-2026-47198 was published on June 30, 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-47198 actively exploited?
CVE-2026-47198 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-47198?
CVE-2026-47198 has a CVSS base score of 8.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-47198?
A fix for CVE-2026-47198 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-47198 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-47198

Explore →

Is Your Infrastructure Affected by CVE-2026-47198?

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