dbcve.org
Urvanov Syntax HighlighterWordPress extension · Urvanov

CVE-2023-45106

HIGH · 8.8 CVSS v3.1 Published 2023-10-12
Fix available
A fix is available. Upgrade to after 2.8.33 or later.
See remediation →
95/100
Remediation priority · Urgent
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 Fedor Urvanov, Aram Kocharyan Urvanov Syntax Highlighter plugin <= 2.8.33 versions.

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

Cross-Site Request Forgery (CSRF) vulnerability in Urvanov Syntax Highlighter plugin versions 2.8.33 and below allows attackers to induce authenticated administrators to perform unwanted actions (e.g., modifying plugin settings, injecting malicious code via shortcodes) by tricking them into visiting crafted URLs.

MitigationUpdate Urvanov Syntax Highlighter plugin to a version higher than 2.8.33 which includes proper CSRF token validation for all state-changing 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
Urvanov Syntax HighlighterWordPress extension
Affected:<= 2.8.33

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

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

  1. Confirm Urvanov Syntax Highlighter plugin is installed
    Access your WordPress admin dashboard, navigate to the Plugins section, and locate Urvanov Syntax Highlighter (may also appear as Syntax Highlighter or Urvanov Syntax Highlighter) in the installed plugins list.
    Affected if The plugin appears in your WordPress plugins list and is activated.
  2. Identify the installed plugin version
    In the WordPress plugins list, click on the plugin name or view its details to find the version number displayed alongside the plugin name.
    Affected if The displayed version number is 2.8.33 or any version lower than 2.8.33.
  3. Verify the vulnerability range
    Compare your installed version against the affected range: any version up to and including 2.8.33 is vulnerable.
    Affected if Your version is 2.8.33 or lower (for example, 2.8.32, 2.8.30, 2.0.0, etc.).
  4. Confirm administrator accounts exist
    CSRF attacks target authenticated administrators. Check if any administrator-level user accounts exist on the WordPress site by navigating to Users > All Users in the admin dashboard.
    Affected if There is at least one active administrator user account on the site.

You are affected if the Urvanov Syntax Highlighter plugin is installed with version 2.8.33 or lower and your site has administrator accounts, since the CSRF flaw can be exploited through crafted URLs to trick logged-in admins into making unintended state-changing requests.

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.8.33
Interim mitigation

Update Urvanov Syntax Highlighter plugin to a version higher than 2.8.33 which includes proper CSRF token validation for all state-changing requests.

Recommended fix Moderate confidence

Latest available version (any release above 2.8.33)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Find the Urvanov Syntax Highlighter plugin
  4. Check for available updates or navigate to the plugin's page to download the latest version
  5. Update to the latest version available (any version above 2.8.33)

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

Fix this in Urvanov Syntax Highlighter Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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