Code Snippets ExtendedWordPress extension · Code Snippets Extended Project
CVE-2022-29436
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 · uneditedPersistent Cross-Site Scripting (XSS) vulnerability in Alexander Stokmann's Code Snippets Extended plugin <= 1.4.7 on WordPress via Cross-Site Request Forgery (vulnerable parameters &title, &snippet_code).
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 · high confidencePersistent XSS in Code Snippets Extended plugin allows injection of malicious JavaScript through the title and snippet_code parameters via CSRF. An attacker can trick an authenticated administrator into submitting a crafted form that stores malicious scripts in the database, which then executes when viewed by other users.
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 ExtendedWordPress extension
<= 1.4.7CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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.
-
Confirm Code Snippets Extended plugin is installedCheck the WordPress plugins directory for 'code-snippets-extended' folder or look for the plugin in wp-admin > Plugins. Also check wp_options table for any 'code_snippets_extended' related entries.Affected if The plugin folder or database entries exist in the WordPress installation.
-
Identify the installed plugin versionOpen the main plugin PHP file (usually code-snippets-extended.php) and locate the version comment in the plugin header, or check the readme.txt file for the Version field.Affected if The version number is 1.4.7 or lower.
-
Verify CSRF protection is missing on snippet submission formsInspect the PHP file handling form submissions for snippet_code and title parameters. Search for wp_nonce_field, nonce_verify, or verify_nonce functions. Check if these functions are NOT present in the form handling code.Affected if The form processing code lacks nonce verification or CSRF token validation.
-
Check for stored XSS in snippet recordsQuery the WordPress database: SELECT * FROM wp_posts WHERE post_type = 'snippet' (or relevant custom post type used by the plugin) and examine the post_title and post_content fields for unsanitized script tags, iframe tags, or event handlers like onerror, onload.Affected if Database contains snippet records with raw script tags or HTML in title/content fields that could execute JavaScript.
A user is affected if the Code Snippets Extended plugin version is 1.4.7 or lower AND the plugin handles title/snippet_code parameters without CSRF nonce validation and output escaping.
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 dataUpdate to patched version when available and implement proper CSRF token validation with nonce checks on all form submissions, plus output escaping for title and code content.
Fix this in Code Snippets Extended
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2022-29436 — 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-2022-29436 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