dbcve.org
Code SnippetsWordPress extension · Codesnippets

CVE-2022-25617

MEDIUM · 6.1 CVSS v3.1 Published 2022-05-18
Fix available
A fix is available. Upgrade to after 2.14.3 or later.
See remediation →
68/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
Reflected Cross-Site Scripting (XSS) vulnerability in Code Snippets plugin <= 2.14.3 at WordPress via &orderby vulnerable parameter.

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 confidence

Reflected Cross-Site Scripting (XSS) vulnerability in the Code Snippets WordPress plugin (versions <= 2.14.3). The 'orderby' parameter in admin pages is not properly sanitized, allowing attackers to inject malicious JavaScript via crafted URLs that are reflected back to users.

MitigationUpdate the Code Snippets plugin to version 2.14.4 or later, which contains the security patch. If immediate update is not possible, implement output escaping on the orderby parameter using WordPress sanitization functions like sanitize_text_field() and esc_attr().

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
Affected:<= 2.14.3

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
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 checks

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

  1. Verify Code Snippets plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Code Snippets' in the list, or check the plugin files in wp-content/plugins/code-snippets/ for a version file
    Affected if The Code Snippets plugin is not present on the WordPress site
  2. Determine installed plugin version
    Check the plugin version number displayed in the WordPress Plugins admin page, or open the main plugin file (e.g., code-snippets/code-snippets.php) and look for the 'Version' header comment
    Affected if The installed version is 2.14.3 or earlier
  3. Identify if admin access is available
    Verify you have administrative access to the WordPress backend where the Code Snippets plugin admin pages are accessible
    Affected if You have admin access to a WordPress site running the Code Snippets plugin
  4. Test vulnerable parameter reflection
    Navigate to any Code Snippets admin page (such as the Snippets list), then add '?orderby=<script>alert(1)</script>' to the URL and observe if the value is reflected unescaped in the page HTML
    Affected if The orderby parameter value is reflected back into the HTML without proper escaping (the script tag appears literally in the page source)

You are affected if the Code Snippets plugin version is 2.14.3 or earlier AND you have admin access to the WordPress admin area where the plugin is active, with the orderby parameter being reflected without sanitization.

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 2.14.3
Interim mitigation

Update the Code Snippets plugin to version 2.14.4 or later, which contains the security patch. If immediate update is not possible, implement output escaping on the orderby parameter using WordPress sanitization functions like sanitize_text_field() and esc_attr().

Recommended fix Moderate confidence

Code Snippets 2.14.4 or later (latest stable release)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the Code Snippets plugin
  4. Check the current version number
  5. If current version is 2.14.3 or earlier, click 'Update Now' to upgrade to the latest version
  6. Alternatively, download the latest version from wordpress.org and upload via Plugins > Add New > Upload Plugin
  7. After update, verify the new version number in the plugins list
Caveat Minimal risk - this is a minor version update containing security fixes; review changelog for any functional changes

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

Fix this in Code Snippets Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-25617 — 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-25617 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