CVE-2026-55219: Paymenter race condition in credit payment implementation

CVE-2026-55219 · Severity: medium · CVSS 5.3 · Published 2026-07-20

Paymenter is an open-source platform used to manage hosting services and digital storefronts. A flaw in how the system handles credit payments allows users to bypass their balance limits by submitting multiple payment requests at the exact same time. This could result in customers receiving services or digital goods without sufficient funds, leading to direct financial loss for the hosting provider.

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

Quick answers

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

Technical details

A race condition exists in the payWithCredit() function within app/Livewire/Invoices/Show.php. The application attempts to use a pessimistic row lock (lockForUpdate()) to protect the user's credit balance; however, this lock is executed outside of a formal database transaction. In MySQL and MariaDB environments, row-level locks are ignored unless they are enclosed within a transaction. An authenticated attacker can exploit this by sending concurrent payment requests, causing the application to read the same sufficient balance for multiple transactions before any single transaction has deducted the funds. This results in a 'double-spend' scenario where services are provisioned via ExtensionHelper::addPayment() despite insufficient total credit. The issue is resolved in version 1.5.5.

Affected products

  • Paymenter Paymenter < 1.5.5

Identifiers

  • CVE-2026-55219
  • GHSA-pgcq-8grm-5rx9

Timeline

  • 2026-06-30: advisory: GitHub security advisory published by developer
  • 2026-07-20: disclosed: CVE-2026-55219 published to NVD
  • 2026-07-20: patched: Fix released in version 1.5.5

References

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