LiveActive security incident?Get immediate response
CVE Record

CVE-2023-35880: WordPress WooCommerce Brands Plugin <= 1.6.49 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in WooCommerce WooCommerce Brands plugin <= 1.6.49 versions.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This CVE affects the WooCommerce Brands WordPress plugin at versions 1.6.49 and earlier. A successful attack would require tricking a user into interacting with a malicious request, potentially causing limited unauthorized changes or disruption. The source bundle does not identify stolen data risk or confirmed real-world exploitation.

Executive priority

Treat this as a moderate WordPress hygiene issue. It should be handled in the normal vulnerability remediation cycle, faster for ecommerce sites where unauthorized catalog or brand changes could affect operations or customer trust.

Technical view

CVE-2023-35880 is a CSRF issue in WooCommerce Brands <= 1.6.49, mapped to CWE-352. CVSS 3.1 is 5.4 with network reachability, low complexity, no attacker privileges, and required user interaction. The bundle does not name the affected endpoint, exact action, or fixed version.

Likely exposure

Exposure is limited to WordPress sites with the WooCommerce Brands plugin installed at version 1.6.49 or earlier. Sites not using this plugin are not exposed based on the provided sources.

Exploitation context

The bundle does not show CISA KEV listing or cite active exploitation. Exploitation would require user interaction, consistent with CSRF, likely targeting an authenticated site user to trigger an unintended state-changing action.

Researcher notes

Evidence is thin beyond CVE metadata and the PatchStack entry. The source bundle confirms CSRF class, affected plugin range, CVSS vector, and no KEV signal, but not endpoint details, proof-of-concept availability, or a specific fixed version.

Mitigation direction

  • Inventory WordPress sites for WooCommerce Brands and confirm installed versions.
  • For <=1.6.49, follow WooCommerce or PatchStack guidance for remediation.
  • Update the plugin if a vendor-confirmed fixed release is available.
  • Disable or remove the plugin where it is not business-critical.
  • Restrict administrative access until remediation status is confirmed.

Validation and detection

  • Check each WordPress instance for WooCommerce Brands version <=1.6.49.
  • Confirm production, staging, and backup sites share the same plugin review.
  • Review recent administrative changes for unexpected brand-related modifications.
  • Verify vendor advisories for fixed-version or mitigation details.
  • Document affected hosts, remediation status, and remaining exceptions.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

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 lookup
cve · low confidence lookup

CVE-2023-35880 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
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

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2023-35880Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
WooCommerceWooCommerce Brandswoocommerce-brands, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

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.