Accept Stripe Payments <= 2.0.79 — Unauthenticated Content Injection
CVE-2023-48285Published · Updated Action summary
Affected: ≤2.0.79Update to 2.0.80 or newer
All remediation steps- Severity
- Medium5.3
- CVSS
- 5.3CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:NWhat does this vector mean?
AV:NAttack vector- Network
AC:LAttack complexity- Low
PR:NPrivileges required- None
UI:NUser interaction- None
S:UScope- Unchanged
C:NConfidentiality- None
I:LIntegrity- Low
A:NAvailability- None
- Required access
- No account needed
- Exploit prediction (EPSS)
- No score
- CISA KEV
- Not listed
On this page8
Am I affected?
Accept Stripe Payments stripe-payments
- Affected≤ 2.0.79
- Patched in2.0.80
Update to 2.0.80 or newer.
You are affected if you run ≤ 2.0.79. Version 2.0.80 and later are not affected by this issue.
- Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Accept Stripe Payments.
- No admin access? Run a passive check of your site. It reads public files only.
- No account is needed to exploit this. Treat any exposed site on an affected version as at risk.
What to do
- Update to version 2.0.80, or a newer patched version
- Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
- Watch Accept Stripe Payments to get an email when the next vulnerability is published.
Advisory
Source description from Wordfence Intelligence, credited to Joshua Chan.
The Accept Stripe Payments plugin for WordPress is vulnerable to Content Injection in all versions up to, and including, 2.0.79. This is due to payment data not properly being sanitized in the get_billing_details() function. This makes it possible for unauthenticated attackers to inject arbitrary content into pages.
Exploits & references
Proof-of-concept & detection
No public proof-of-concept or detection template is known for this vulnerability.
Advisories & patches
- Advisorywordfence.com
Related CVEs
More in Accept Stripe Payments
All 9| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium5.3 | Unauthenticated Insecure Direct Object Reference <2.1.4Update to 2.1.4 | CVE-2026-81424 | |
| Medium6.1 | Unauthenticated Open Redirect <2.1.4Update to 2.1.4 | CVE-2026-81423 | |
| High7.2 | Unauthenticated Stored Cross-Site Scripting ≤2.1.2Update to 2.1.3 | CVE-2026-78282 | |
| Medium5.3 | Unauthenticated Payment Bypass ≤2.0.98Update to 2.0.99 | CVE-2026-42752 | |
| Medium5.4 | Authenticated (Contributor+) Stored Cross-Site Scripting via accept_stripe_payment_ng Shortcode ≤2.0.86Update to 2.0.87 | CVE-2024-7353 |
- Medium5.3Unauthenticated Insecure Direct Object Reference
<2.1.4Update to 2.1.4
- Medium6.1Unauthenticated Open Redirect
<2.1.4Update to 2.1.4
- High7.2Unauthenticated Stored Cross-Site Scripting
≤2.1.2Update to 2.1.3
- Medium5.3Unauthenticated Payment Bypass
≤2.0.98Update to 2.0.99
- Medium5.4Authenticated (Contributor+) Stored Cross-Site Scripting via accept_stripe_payment_ng Shortcode
≤2.0.86Update to 2.0.87
Timeline
CVE published
Severity medium, CVSS 5.3
Record last updated
Sources & licenses
Wordfence record- Vulnerability data
- Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
- CVE® identifiers
- Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
- CVSS / CWE
- National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
- VulnCrest content
- Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.