CVE Explore

Vulnerability in Paymenter

CVE-2026-55219

CVSS v3
5.3 Medium
Public exploits
None known
EPSS
0.002 · 11.8th percentile
Published
2026-07-20

What to do

Fixed in
1.5.5
Affected
1 affected product

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.

Vulnerability class: Race Condition

Published · last modified .

CVSS v3 metric

CVSS v3 base score 5.3 (Medium). Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N.

Attack Vector
Network AV:N
Attack Complexity
High AC:H
Privileges Required
Low PR:L
User Interaction
None UI:N
Scope
Unchanged S:U
Confidentiality
None C:N
Integrity
High I:H
Availability
None A:N

EPSS exploit prediction

EPSS 0.002, 11.8th percentile (last changed ); unchanged over 30 days. About EPSS.

Affected products

Weakness classification (CWE)

References