Security readout for executives and security teams
Plain-English summary
This CVE affects WordPress sites using the WooCommerce Stripe Payment Gateway plugin through version 7.6.0. It is a CSRF issue, meaning a logged-in user could be tricked into causing an unintended change. The cited severity is medium, with limited integrity and availability impact and no confidentiality impact stated.
Executive priority
Treat this as a moderate-priority WordPress plugin issue. It is not cited as actively exploited, but payment gateway configuration is business-sensitive, so affected ecommerce sites should be inventoried and updated through normal security maintenance windows.
Technical view
CVE-2023-44999 is a CWE-352 Cross-Site Request Forgery vulnerability in WooCommerce Stripe Payment Gateway through 7.6.0. The CVSS 3.1 score is 5.4 with network attack vector, low complexity, no privileges required, and required user interaction. The provided sources do not identify the affected endpoint, action, or fixed version.
Likely exposure
Exposure is limited to WordPress installations running WooCommerce Stripe Payment Gateway version 7.6.0 or earlier. Sites not using this plugin, or using versions outside the affected range, are not indicated as affected by the provided sources.
Exploitation context
The source bundle does not show CISA KEV listing or cite active exploitation. User interaction is required. Because this is CSRF, realistic risk depends on whether an authenticated user can be induced to perform an unintended browser action.
Researcher notes
Public details in the bundle are sparse. The sources provide affected product, affected range, CWE, and CVSS, but not endpoint details, exploit preconditions beyond user interaction, proof of exploitation, or a named fixed version.
Mitigation direction
- Inventory WooCommerce Stripe Payment Gateway versions across WordPress sites.
- Check WooCommerce or Patchstack guidance for the fixed version.
- Upgrade affected installations once a vendor-confirmed fix is identified.
- Review administrative access and reduce unnecessary privileged accounts.
Validation and detection
- Confirm whether the plugin is installed on each WordPress site.
- Record installed plugin versions and flag versions 7.6.0 or earlier.
- Review vendor advisories for fixed-version and remediation confirmation.
- Check site logs for unexpected payment gateway setting changes.
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-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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-44999 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
- Medium
- CVSS
- 5.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/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.
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:R/S:U/C:N/I:L/A:L2.82.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
Source materials
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.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.