Code SnippetsWordPress extension
CVE-2023-47666
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-Site Request Forgery (CSRF) vulnerability in Code Snippets Pro Code Snippets.This issue affects Code Snippets: from n/a through 3.5.0.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in Code Snippets Pro plugin allows attackers to trick authenticated administrators into performing unintended actions (such as modifying snippets, changing settings, or executing code) by forcing their browser to send malicious requests.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Code SnippetsWordPress extension
<= 3.5.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Code Snippets Pro installationCheck WordPress plugins directory or wp-content/plugins/code-snippets-pro folder. Look for the main plugin file (usually code-snippets-pro.php) and read its header comment for the Version field.Affected if Code Snippets Pro plugin is installed and the version number is 3.5.0 or lower.
-
Confirm plugin is activeIn WordPress admin dashboard, navigate to Plugins > Installed Plugins and verify that Code Snippets Pro is activated.Affected if The plugin is active and a logged-in administrator can trigger the vulnerable actions.
-
Check for nonce implementation in plugin actionsInspect the plugin PHP files for form submissions and AJAX handlers. Search for presence of 'wp_verify_nonce' or 'check_admin_referer' functions when handling admin actions. If these checks are missing or improperly implemented, the plugin is vulnerable.Affected if Plugin actions (snippet modifications, settings changes, code execution) lack proper WordPress nonce verification.
-
Verify WordPress nonces are required for admin actionsTest by attempting to submit a modified snippet request without a valid nonce parameter (_wpnonce). If the request succeeds without rejection, the CSRF protection is missing.Affected if Admin actions complete successfully without requiring a valid nonce token from the authenticated session.
You are affected if Code Snippets Pro version 3.5.0 or lower is installed and active, and the plugin lacks proper nonce verification on its admin action handlers.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement WordPress nonces on all form submissions and AJAX action handlers to verify request authenticity and prevent forged requests from malicious sites.
Fix this in Code Snippets
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47666 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-47666 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data