Payment bypass via unvalidated wallet amount
Published Aug 12, 2026 · Updated Aug 12, 2026
Payment bypass in WP Swings Wallet System for WooCommerce before 2.7.10 allows remote authenticated users to complete unpaid orders. The partial-payment AJAX handlers trust the client-supplied wallet_amount and apply it as a negative cart fee without checking the stored balance. A customer account, enabled wallet system, purchasable item, and valid front-end nonce are required; exploitation can reduce the order total to zero without debiting the wallet.
Summary
What happened
Payment bypass in WP Swings Wallet System for WooCommerce before 2.7.10 allows remote authenticated users to complete unpaid orders. The partial-payment AJAX handlers trust the client-supplied wallet_amount and apply it as a negative cart fee without checking the stored balance. A customer account, enabled wallet system, purchasable item, and valid front-end nonce are required; exploitation can reduce the order total to zero without debiting the wallet.
The record
- CVE
- CVE-2026-15045
- Published
- Aug 12, 2026
- Updated
- Aug 12, 2026
- Vendor
- WP Swings
- Product
- Wallet System for WooCommerce
- Classifications
- CWE-472
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 12, 2026CVE publishedPublication date reported by the CVE source.
- Aug 12, 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=0 <2.7.10
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.
Weakness, pattern, technique
Public exploit references
- WPScan checkout price manipulation proof of conceptproof of concept · demonstrated
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo