Spendable credit inflation via unlocked downgrade refunds
Published Sep 18, 2026 · Updated Sep 18, 2026
Race condition in Paymenter before 1.5.7 allows remote authenticated users to inflate spendable credit through concurrent service downgrades. The doUpgrade method checks for pending upgrades without a transaction or row lock, then separately inserts an upgrade and increments account credit. An authenticated customer must own an active downgradable service; parallel downgrade requests can yield multiple refunds for one downgrade and fund later invoices or services.
Summary
What happened
Race condition in Paymenter before 1.5.7 allows remote authenticated users to inflate spendable credit through concurrent service downgrades. The doUpgrade method checks for pending upgrades without a transaction or row lock, then separately inserts an upgrade and increments account credit. An authenticated customer must own an active downgradable service; parallel downgrade requests can yield multiple refunds for one downgrade and fund later invoices or services.
The record
- CVE
- CVE-2026-71537
- Published
- Sep 18, 2026
- Updated
- Sep 18, 2026
- Vendor
- Paymenter
- Product
- Paymenter
- Classifications
- CWE-362, T1657
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 18, 2026CVE publishedPublication date reported by the CVE source.
- Sep 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.5.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started