LiveActive security incident?Get immediate response
CVE Record

CVE-2023-47687: WordPress Woo Custom and Sequential Order Number Plugin <= 2.6.0 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in VJInfotech Woo Custom and Sequential Order Number plugin <= 2.6.0 versions.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

A WordPress WooCommerce order-numbering plugin has a CSRF flaw. If a privileged logged-in user is tricked into interacting with hostile content, site settings or workflow data could be changed with limited integrity impact. The sources do not report data theft, outage impact, or confirmed exploitation.

Executive priority

Treat as a moderate operational risk for WooCommerce sites using this plugin. Prioritize inventory and remediation during normal patch cycles, faster for stores where order numbering affects finance, fulfillment, or compliance workflows.

Technical view

CVE-2023-47687 is CWE-352 in VJInfotech Woo Custom and Sequential Order Number for WordPress through version 2.6.0. CVSS 3.1 is 4.3: network reachable, low complexity, user interaction required, low integrity impact, no stated confidentiality or availability impact.

Likely exposure

Exposure is limited to WordPress sites running the Woo Custom and Sequential Order Number plugin at version 2.6.0 or earlier. The bundle does not identify affected CPEs or a fixed version.

Exploitation context

The CVE is not listed as KEV, and the provided sources do not state active exploitation. CSRF generally depends on inducing a logged-in authorized user to perform an unintended browser action.

Researcher notes

Available evidence is sparse: the bundle names CSRF, version boundary <=2.6.0, CVSS, and Patchstack reference only. No public exploit status, fixed version, endpoint detail, or precise vulnerable action is provided here.

Mitigation direction

  • Inventory WordPress sites for the affected plugin and version.
  • Check vendor or Patchstack guidance for a fixed release or official mitigation.
  • Update the plugin if an official fixed version is available.
  • Disable or remove the plugin where it is not operationally required.
  • Restrict administrative access and review privileged user hygiene.

Validation and detection

  • Confirm whether the plugin slug is installed on each WordPress site.
  • Record installed plugin versions and flag version 2.6.0 or earlier.
  • Review vendor and Patchstack advisories for current remediation status.
  • Check administrative audit logs for unexpected order-numbering configuration changes.
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-47687 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:N/UI:R/S:U/C:N/I:L/A:N

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:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2023-47687Attack 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:N

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
VJInfotechWoo Custom and Sequential Order Numberwoo-custom-and-sequential-order-number, 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.