Vulnerability in paymenter/paymenter (CVE-2026-55219)
Summary
Vulnerability in paymenter/paymenter (CVE-2026-55219). Data can be tampered with by attackers. Mitigation: upgrade to 1.5.5 or later.
Original description
The description as published by the 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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-55219 has been found in paymenter/paymenter.
Data can be tampered with by attackers. CVSS score: 5.3/10.
What to do: upgrade paymenter/paymenter to 1.5.5 or later.
If unsure, ask your IT team or search "paymenter/paymenter CVE-2026-55219" on the vendor's site.
CVE-2026-55219 (paymenter/paymenter) — CWE-362 / CVSS v3 5.3
Attack vector: remote (network-reachable) / no user interaction
Patched: 1.5.5 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-362) exists in paymenter/paymenter.
Check the vendor advisory for the affected versions of paymenter/paymenter.
Severity: Medium (CVSS 5.3/10). Data can be tampered with by attackers.
Update to 1.5.5.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'paymenter/paymenter' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'paymenter/paymenter' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
paymenter/paymenterを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade paymenter/paymenter to 1.5.5ステージング環境で 1.5.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- web github.com