dbcve.org
Code Snippets ExtendedApplication · Code Snippets Extended Project

CVE-2022-29435

MEDIUM · 5.4 CVSS v3.1 Published 2022-05-17
Fix available
A fix is available. Upgrade to after 1.4.7 or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Cross-Site Request Forgery (CSRF) vulnerability in Alexander Stokmann's Code Snippets Extended plugin <= 1.4.7 on WordPress allows an attacker to delete or to turn on/off snippets.

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 confidence

This is a Cross-Site Request Forgery (CSRF) vulnerability in the Code Snippets Extended WordPress plugin versions 1.4.7 and below. The plugin lacks proper anti-CSRF token validation when handling snippet deletion and on/off toggle actions, allowing attackers to craft malicious requests that trick authenticated administrators into performing unintended operations on snippets.

MitigationUpdate the Code Snippets Extended plugin to the latest patched version that implements proper nonce validation for all state-changing actions. Additionally, implement SameSite cookie attributes and referer/origin header validation as defense-in-depth measures.

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 Snippets ExtendedApplication
Affected:<= 1.4.7

CVSS 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
None
Integrity
Low
Availability
Low

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Code Snippets Extended plugin is installed
    Navigate to WordPress admin dashboard > Plugins and look for 'Code Snippets Extended' in the list of installed plugins. Check if it is activated.
    Affected if The plugin is installed and activated on the WordPress site
  2. Check the installed version
    In the Plugins list, find Code Snippets Extended and view the version number displayed beneath the plugin name. Compare this against the affected range: versions 1.4.7 and below.
    Affected if The installed version is 1.4.7 or lower
  3. Inspect the delete snippet functionality for nonce validation
    Locate the plugin file handling snippet deletion (typically in the admin menu or AJAX handler). Search the code for the presence of a nonce check (wp_verify_nonce or check_admin_referer) before the snippet deletion logic executes.
    Affected if No nonce verification is performed before allowing snippet deletion (the delete action proceeds without validating a security token)
  4. Inspect the toggle on/off functionality for nonce validation
    Locate the plugin file handling the snippet toggle action. Search for nonce validation code (wp_verify_nonce, check_admin_referer, or similar) preceding the toggle logic.
    Affected if No nonce verification is performed before allowing the snippet state toggle (the on/off action proceeds without validating a security token)

A site is affected if Code Snippets Extended plugin version 1.4.7 or lower is installed and the delete or toggle actions lack proper nonce validation checks in the source code.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 1.4.7
Interim mitigation

Update the Code Snippets Extended plugin to the latest patched version that implements proper nonce validation for all state-changing actions. Additionally, implement SameSite cookie attributes and referer/origin header validation as defense-in-depth measures.

Recommended fix Moderate confidence

Version 1.4.8 or latest available on wordpress.org

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Code Snippets Extended' in the plugin list
  4. Click 'Update now' if an update is available, or download the latest version from wordpress.org
  5. Verify the update is to version 1.4.8 or higher
  6. Test that snippets can be created, edited, deleted, and toggled normally
  7. Consider implementing additional CSRF protection via WordPress nonces for any custom code interacting with this plugin

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Code Snippets Extended Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-29435 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-29435 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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