LiveActive security incident?Get immediate response
CVE Record

CVE-2023-47666: WordPress Code Snippets Plugin <= 3.5.0 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Code Snippets Pro Code Snippets.This issue affects Code Snippets: from n/a through 3.5.0.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-47666 is a CSRF flaw in the WordPress Code Snippets plugin through version 3.5.0. An attacker would need to trick a user into taking an action, which could cause a limited unauthorized change. The source bundle does not show active exploitation or a specific exploit path.

Executive priority

Treat as a routine but real WordPress hygiene issue. It has medium severity and limited integrity impact, but vulnerable plugins on public sites can still create business risk if left unmanaged.

Technical view

The issue is CWE-352 Cross-Site Request Forgery affecting Code Snippets package code-snippets through 3.5.0. CVSS 3.1 is 4.3 with network access, low attack complexity, required user interaction, no confidentiality or availability impact, and low integrity impact.

Likely exposure

Exposure is limited to WordPress sites running the Code Snippets plugin at version 3.5.0 or earlier. Sites not using this plugin, or using versions outside the stated affected range, are not shown as affected in the provided sources.

Exploitation context

The CVE is not listed as KEV in the provided bundle. The available evidence supports a user-interaction CSRF risk, not confirmed active exploitation. Public details in the bundle are sparse, so operational impact should be validated against vendor and Patchstack guidance.

Researcher notes

Evidence identifies CSRF only, with no provided endpoint, nonce failure detail, affected action, or fixed version. Avoid assuming exploitability beyond CVSS UI:R and integrity-low semantics unless vendor or Patchstack details confirm the vulnerable workflow.

Mitigation direction

  • Inventory WordPress sites for the Code Snippets plugin and version.
  • Check vendor or Patchstack guidance for the remediated version.
  • Update affected installations according to trusted vendor guidance.
  • Temporarily disable the plugin where business impact allows.
  • Review admin security controls for high-risk WordPress users.

Validation and detection

  • Confirm whether Code Snippets is installed on each WordPress site.
  • Record the installed plugin version and compare it with 3.5.0.
  • Review Patchstack and vendor advisories for remediation status.
  • Check whether compensating controls exist for administrative user sessions.
  • Monitor security logs for suspicious configuration or snippet 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-47666 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-47666Attack 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
Code Snippets ProCode Snippetscode-snippets, 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.