CVE-2026-55219Network attack vector

Credit double-spend via transactionless row locking

Published Jul 20, 2026 · Updated Jul 20, 2026

Race condition in Paymenter before 1.5.5 allows remote authenticated users to pay multiple invoices with one valid credit balance. The payWithCredit implementation in app/Livewire/Invoices/Show.php calls lockForUpdate() without a database transaction, so concurrent requests read and approve against the same balance. Exploitation requires an authenticated account, a valid credit balance, multiple pending invoices, and precisely concurrent requests; successful payments provision services or digital goods beyond the paid balance.

CVSS severity5.3
Medium
EPSS probability0.21%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Race condition in Paymenter before 1.5.5 allows remote authenticated users to pay multiple invoices with one valid credit balance. The payWithCredit implementation in app/Livewire/Invoices/Show.php calls lockForUpdate() without a database transaction, so concurrent requests read and approve against the same balance. Exploitation requires an authenticated account, a valid credit balance, multiple pending invoices, and precisely concurrent requests; successful payments provision services or digital goods beyond the paid balance.

The record

CVE
CVE-2026-55219
Published
Jul 20, 2026
Updated
Jul 20, 2026
Vendor
Paymenter
Product
Paymenter
Classifications
CWE-362, T1565.001
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Jul 20, 2026CVE publishedPublication date reported by the CVE source.
  2. Jul 20, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 1.5.5

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Paymenter · Paymenterversion=< 1.5.5

Published CVSS scores

5.3GitHubCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-362Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
T1565.001Stored Data Manipulation

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo