Security readout for executives and security teams
Plain-English summary
CVE-2023-51499 is a broken access control issue in WooCommerce Shipping Per Product for WordPress, affecting versions through 2.5.4. A logged-in low-privilege user may access information they should not. Public data rates it medium, with limited confidentiality impact and no stated integrity or availability impact.
Executive priority
Treat as a moderate website risk. Prioritize internet-facing WooCommerce sites with customer accounts, but this is not supported as emergency-level without exploitation evidence.
Technical view
The CVE maps to CWE-862 Missing Authorization. CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N indicates network reachability, low complexity, authentication required, and confidentiality-only impact. The bundle does not identify affected endpoints, fixed versions, or exploit mechanics.
Likely exposure
Exposure is limited to WordPress sites running WooCommerce Shipping Per Product version 2.5.4 or earlier, especially sites allowing low-privilege user accounts.
Exploitation context
The source bundle does not show CISA KEV listing or cite active exploitation. Risk depends on whether untrusted authenticated users exist on the WordPress site.
Researcher notes
Evidence is limited to CVE metadata and a Patchstack VDB reference. The bundle does not provide endpoint details, proof of concept, exploit status, or fixed-version information.
Mitigation direction
- Inventory WordPress sites using WooCommerce Shipping Per Product.
- Identify installations at version 2.5.4 or earlier.
- Check WooCommerce, WordPress, or Patchstack guidance for a fixed release.
- Limit unnecessary low-privilege accounts until vendor guidance is applied.
- Review plugin access controls and role assignments.
Validation and detection
- Confirm plugin name and version on each WordPress site.
- Check whether public registration or customer accounts are enabled.
- Review roles for unnecessary low-privilege access.
- Look for vendor advisories naming a fixed version.
- Confirm remediation with authenticated role-based access testing.
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-51499 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
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
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:L/UI:N/S:U/C:L/I:N/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
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.
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.