CVE-2026-71537: Paymenter/paymenter Paymenter Has A Credit-refund Double-spend Vulnerability
MODERATECVE-2026-71537 is a MODERATE (CVSS 6.5) paymenter has a credit-refund double-spend vulnerability (CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')) affecting Paymenter/paymenter libraries in the Packagist ecosystem. The issue involves paymenter has a credit-refund double-spend race condition in service downgrade (doupgrade). Remediation is available by upgrading affected packages to version 1.5.7.
CVE-2026-71537 at a Glance
Security Impact
CVSS: 6.5
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N).
How to Fix CVE-2026-71537
To remediate this vulnerability, upgrade all affected Paymenter/paymenter dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade paymenter/paymenter to 1.5.7
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for paymenter/paymenter
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-71537, inspect your project dependencies for Paymenter/paymenter:
inspect dependencies for paymenter/paymenter
Analyze the terminal output to locate any version of Paymenter/paymenter in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.5.7), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'), where the product contains a concurrent code sequence that 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 operating concurrently. In Paymenter/paymenter, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-71537 Affected Paymenter/paymenter Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
paymenter/paymenter
|
Packagist |
< 1.5.7
|
1.5.7
|
References
Frequently Asked Questions
What is CVE-2026-71537?
Which Paymenter/paymenter versions are affected?
What version fixes CVE-2026-71537?
Is paymenter/paymenter affected?
What is the CVSS score of CVE-2026-71537?
What CWE is associated with CVE-2026-71537?
How can I check Packagist dependencies for CVE-2026-71537?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-5gmm-hjfj-8ff7",
"modified" : "2026-09-18T17:58:55Z",
"published" : "2026-09-18T17:58:55Z",
"aliases" : [ "CVE-2026-71537" ],
"summary" : "Paymenter has a credit-refund double-spend race condition in service downgrade (doUpgrade)",
"details" : "### Summary\n\nThe 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.\n\n### Technical Details\n\nThe 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.\n\nOnce 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.\n\n### Impact\n\nThis race condition allows any authenticated customer with an active, downgradable service to inflate their spendable credit balance to an arbitrary multiple of their legitimate refund amount.\n\nBecause the newly granted balance acts as real, spendable store credit, it can be immediately leveraged to settle future platform invoices or provision additional services, resulting in direct financial and resource loss to the operator.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Packagist",
"name" : "paymenter/paymenter"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "1.5.7"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 1.5.6"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/Paymenter/Paymenter/security/advisories/GHSA-5gmm-hjfj-8ff7"
}, {
"type" : "WEB",
"url" : "https://github.com/Paymenter/Paymenter/commit/a42e7f8bafce054ad70de3a2c2ac94d13579f41b"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/Paymenter/Paymenter"
}, {
"type" : "WEB",
"url" : "https://github.com/Paymenter/Paymenter/releases/tag/v1.5.7"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-362" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-09-18T17:58:55Z",
"nvd_published_at" : null
}
}