Security readout for executives and security teams
Plain-English summary
CVE-2023-48286 is a broken access control issue in the WordPress Accept Stripe Payments plugin. Public sources say versions through 2.0.79 are affected. An unauthenticated remote attacker could affect integrity and cause limited availability impact. It is high severity, but the provided sources do not show active exploitation.
Executive priority
Treat this as high priority for any WordPress site using this payment plugin. The business concern is unauthorized manipulation of payment-related functionality, not data theft based on the CVSS confidentiality rating provided.
Technical view
The CVE describes missing authorization in mra13 Stripe Payments, package stripe-payments, affecting versions up to and including 2.0.79. It maps to CWE-862 with CVSS 3.1 score 8.2: AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L. The bundle does not identify the vulnerable endpoint or a confirmed fixed version.
Likely exposure
Exposure is likely limited to internet-facing WordPress sites running the Accept Stripe Payments plugin at version 2.0.79 or earlier. General Stripe users and WordPress sites without this plugin are not indicated as affected by the provided sources.
Exploitation context
The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. The CVSS vector still indicates remote, unauthenticated, low-complexity attack conditions, so exposed vulnerable sites warrant prompt review.
Researcher notes
Evidence is incomplete. The provided sources establish missing authorization, affected versions, CWE-862, and CVSS, but do not provide endpoint details, exploit status, or a named fixed version. Avoid assuming broader Stripe platform exposure.
Mitigation direction
- Inventory WordPress sites for the stripe-payments plugin and version.
- If version is 2.0.79 or earlier, check vendor and Patchstack guidance immediately.
- Update to a vendor-confirmed fixed release if one is available.
- Disable or remove the plugin where it is not business-critical.
- Review payment, order, and plugin configuration changes for unauthorized activity.
Validation and detection
- Confirm whether each WordPress site has the Accept Stripe Payments plugin installed.
- Record plugin versions and flag any version 2.0.79 or earlier.
- Check whether the site is publicly reachable and processing payments.
- Review WordPress and web server logs for suspicious unauthenticated plugin access.
- Confirm remediation by rechecking installed plugin version and site functionality.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2023-48286 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L3.94.2PatchstackVulnerability scoring details
Base CVSS 3.1 score
8.2HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/Wordpress/Plugin/stripe-payments/vulnerability/wordpress-accept-stripe-payments-plugin-2-0-79-broken-access-control-vulnerability?_s_id=cveCVE reference, Patchstack · vdb-entry
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.