LiveActive security incident?Get immediate response
CVE Record

CVE-2023-51678: WordPress Doofinder for WooCommerce Plugin <= 2.0.33 is vulnerable to Broken Access Control

Cross-Site Request Forgery (CSRF) vulnerability in Doofinder Doofinder WP & WooCommerce Search.This issue affects Doofinder WP & WooCommerce Search: from n/a through 2.0.33.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a medium-severity issue in the Doofinder WP & WooCommerce Search plugin for WordPress. Affected sites running versions through 2.0.33 may be exposed to a CSRF/broken access control flaw with a reported low availability impact. No source in the bundle confirms active exploitation.

Executive priority

Treat this as a normal-priority WordPress plugin remediation item, not an emergency. Focus on identifying affected ecommerce sites, confirming whether a vendor fix exists, and reducing exposure where the plugin is unnecessary.

Technical view

CVE-2023-51678 is reported as CWE-352 in Doofinder WP & WooCommerce Search through 2.0.33. The CVSS 3.1 vector is 4.3: AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L, indicating low attack complexity, required low privileges, unchanged scope, and low availability impact only.

Likely exposure

Exposure is limited to WordPress or WooCommerce sites with the Doofinder WP & WooCommerce Search plugin installed at version 2.0.33 or earlier. The source bundle does not identify other affected products or confirm a fixed version.

Exploitation context

The CVE is not listed as KEV in the provided bundle, and the cited sources do not state active exploitation. Public evidence here supports vulnerability existence and affected version range, but not exploit availability or observed attacks.

Researcher notes

The record labels the issue as CSRF and broken access control, while the CVSS vector lists PR:L and UI:N. That combination should be validated against the original advisory before deeper risk modeling. Do not assume confidentiality or integrity impact from the provided CVSS data.

Mitigation direction

  • Inventory WordPress sites for the doofinder-for-woocommerce plugin.
  • Prioritize sites running version 2.0.33 or earlier.
  • Check Doofinder and Patchstack guidance for a fixed version or workaround.
  • Update the plugin if a vendor-supported fixed release is available.
  • Disable or remove the plugin where it is unnecessary.

Validation and detection

  • Confirm plugin name and version from WordPress administration or asset inventory.
  • Verify whether each instance is version 2.0.33 or earlier.
  • Check vendor or Patchstack records for remediation status.
  • Review recent administrative activity for unexpected plugin-related changes.
  • Document remaining exposure where no fixed version is confirmed.
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-51678 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
4.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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
DoofinderDoofinder WP & WooCommerce Searchdoofinder-for-woocommerce, 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.