Paymenter up to 1.5.4 Payment Show.php lockForUpdate race condition

Summaryinfo

A vulnerability labeled as critical has been found in Paymenter up to 1.5.4. Affected by this vulnerability is the function lockForUpdate of the file app/Livewire/Invoices/Show.php of the component Payment. The manipulation results in race condition. This vulnerability is cataloged as CVE-2026-55219. The attack may be launched remotely. There is no exploit available.

Detailsinfo

A vulnerability classified as critical has been found in Paymenter up to 1.5.4. Affected is the function lockForUpdate of the file app/Livewire/Invoices/Show.php of the component Payment. The manipulation with an unknown input leads to a race condition vulnerability. CWE is classifying the issue as CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

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.

The advisory is available at github.com. This vulnerability is traded as CVE-2026-55219 since 06/16/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. Successful exploitation requires user interaction by the victim. Technical details are known, but there is no available exploit.

By approaching the search of inurl:app/Livewire/Invoices/Show.php it is possible to find vulnerable targets with Google Hacking.

Upgrading to version 1.5.5 eliminates this vulnerability.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Name

• Paymenter

Version

• 1.5.0
• 1.5.1
• 1.5.2
• 1.5.3
• 1.5.4

Website

• Product: https://github.com/Paymenter/Paymenter/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion