CVE-2026-55219

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (11th 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

Also known asEUVD-2026-46097 (ENISA EUVD) · GHSA-pgcq-8grm-5rx9 (GitHub Security Advisories)Source: ENISA EUVD

5.3EG
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.2%CVSS: 5.3Exploit: 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.5, the credit payment implementation in app/Livewire/Invoices/Show.php executes a pessimistic row lock (lockForUpdate()) outside of an active database transaction. Because MySQL/MariaDB requires an enclosing transaction to enforce row-level locks, the guard is ineffective. Concurrent payment requests can exploit this race condition to read the same credit balance simultaneously, allowing users to pay multiple invoices using the same credit balance. In database systems like MySQL, a row lock only works inside a formal transaction; without one, the lock is completely ignored. Because there is no active lock, two payment requests sent at the exact same millisecond can look at the database at the same time. Both requests see the original credit balance, decide it is sufficient, and approve the payment. Because the payment processes successfully through ExtensionHelper::addPayment(), the application provisions the corresponding services or digital goods, resulting in direct financial or resource loss to the platform. This issue has been fixed in version 1.5.5.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
24
EG Risk 24/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity53% × 45%
Impact severity (EG Severity): CVSS 5.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 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.2%
EPSS %ILE
11th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.

EG Severity
5.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

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)

Race condition in payWithCredit() enables credit double-spend · Advisory · Paymenter/Paymenter · GitHub

https://github.com/Paymenter/Paymenter/security/advisories/GHSA-pgcq-8grm-5rx9

Vendor Advisories for CVE-2026-55219(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.5.4 (33 versions)
  • every version up to 1.5.5: fixed in 1.5.5
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 38× 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 129 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 29 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-55219?
CVE-2026-55219 is a medium-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.5, the credit payment implementation in app/Livewire/Invoices/Show.php executes a pessimistic row lock (lockForUpdate()) outside of an active database transaction. Because MySQL/MariaDB…
When was the CVE record for CVE-2026-55219 published?
The CVE record for CVE-2026-55219 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-55219 actively exploited?
CVE-2026-55219 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55219?
CVE-2026-55219 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55219?
A fix for CVE-2026-55219 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-55219 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-55219

Explore →

Is Your Infrastructure Affected by CVE-2026-55219?

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

Book a Demo →Browse All CVEs