Vulnerability in paymenter/paymenter (CVE-2026-71537)
Summary
Vulnerability in paymenter/paymenter (CVE-2026-71537). Data can be tampered with by attackers. Mitigation: upgrade to 1.5.7 or later.
Original description
The description as published by the source.
Summary
The service downgrade implementation in app/Livewire/Services/Upgrade.php::doUpgrade() executes a proration calculation and a subsequent user credit refund without any transactional safety or database locks. The only concurrency check relies on an unisolated database query checking for existing pending upgrades. Because there is no active database transaction or pessimistic row-level lock spanning this validation and the subsequent credit update, concurrent downgrade requests can bypass the guard simultaneously. This allows a user to trigger multiple refunds for a single service downgrade.
Technical Details
The issue occurs because the application verifies eligibility using an unlocked read operation (Service::upgradable) which checks if a pending upgrade row exists. Since there is no enclosing DB::transaction or lockForUpdate(), multiple requests sent in parallel can all query the database at the same millisecond, observe that no pending upgrade exists, and pass the safety check.
Once passed, each concurrent request inserts its own pending upgrade record and executes $credit->increment('amount', abs($price)). Because the balance updates are not serialized against the initial check, the user's credit balance is cumulatively inflated by $N$ times the refund amount for a single legitimate downgrade.
Impact
This race condition allows any authenticated customer with an active, downgradable service to inflate their spendable credit balance to an…
Source: NIST National Vulnerability Database 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-71537 has been found in paymenter/paymenter.
Data can be tampered with by attackers. CVSS score: 6.5/10.
What to do: upgrade paymenter/paymenter to 1.5.7 or later.
If unsure, ask your IT team or search "paymenter/paymenter CVE-2026-71537" on the vendor's site.
CVE-2026-71537 (paymenter/paymenter) — CWE-362 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Patched: 1.5.7 — 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 6.5/10). Data can be tampered with by attackers.
Update to 1.5.7.
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.7ステージング環境で 1.5.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web github.com
- web github.com