CVE-2026-55219
MediumCVSS 5.3Exploitation Probability (EPSS)
Low risk12th percentile - higher than 12% of all known CVEs
Summary
Paymenter versions prior to 1.5.5 have a race condition in the credit payment implementation. The row lock (lockForUpdate()) is executed outside an active database transaction, making it ineffective in MySQL/MariaDB. Concurrent payment requests can read the same credit balance and reuse the same funds.
Risk Assessment
An attacker can reuse the same credit to pay multiple invoices, causing direct financial or resource loss to the platform.
Recommendation
Immediately update Paymenter to version 1.5.5 or later.
Other vulnerabilities in Paymenter
See all- CVE-2026-47198High
Paymenter before 1.5.1 has a vulnerability in the checkout component allowing authenticated users to inject arbitrary key-value pairs into server provisioning parameters, potentially overriding resource limits without privileges.
- CVE-2026-44585Medium
In Paymenter prior to version 1.5.0, the ticket creation endpoint accepts a user-supplied service identifier without enforcing ownership validation, allowing authenticated users to create support tickets referencing services belonging to other accounts by modifying the service ID in the request.
- CVE-2026-44584Medium
Paymenter before version 1.5.0 fails to invalidate the email verification state after an email change. A verified account retains its verified status even after switching to an unverified address. This could lead to abuse of features gated behind verified status.
- CVE-2026-44583Medium
Paymenter is a free open-source webshop solution for hosting services. In versions prior to 1.5.0, the PayPal webhook endpoint /extensions/paypal/webhook processes the PAYPAL-CERT-URL HTTP header without validation, allowing attackers to control server-side HTTP request destinations. This value is passed directly into a server-side HTTP request via file_get_contents without allowlist, validation, or signature verification. The vulnerability allows remote unauthenticated attackers to trigger HTTP GET requests to arbitrary external or internal endpoints, potentially leading to blind SSRF and access to internal network services.
Original NVD description (English source)
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.