Unauthenticated underpayment via unchecked purchase currency
Published Dec 9, 2024 · Updated May 11, 2026
Missing authorization in Accept Stripe Payments 2.0.79 and earlier allows remote attackers to alter purchase currency without authentication. The handle_create_pi() function creates a payment intent without a capability check or server-side validation of the submitted currency. Any site exposing the plugin's checkout can accept a mismatched currency, allowing an unauthenticated buyer to pay less than the configured amount.
Summary
What happened
Missing authorization in Accept Stripe Payments 2.0.79 and earlier allows remote attackers to alter purchase currency without authentication. The handle_create_pi() function creates a payment intent without a capability check or server-side validation of the submitted currency. Any site exposing the plugin's checkout can accept a mismatched currency, allowing an unauthenticated buyer to pay less than the configured amount.
The record
- CVE
- CVE-2023-48286
- Published
- Dec 9, 2024
- Updated
- May 11, 2026
- Vendor
- Stripe
- Product
- Stripe Payments
- Classifications
- CWE-862, CAPEC-180, T1565.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 9, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 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.0.79 changes=[{"at":"2.0.80","status":"unaffected"}]
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
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo