CVE-2024-54407
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 a328496647 CK and SyntaxHighlighter ck-and-syntaxhighlighter allows Stored XSS.This issue affects CK and SyntaxHighlighter: from n/a through <= 3.4.2.
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 confidenceA CSRF vulnerability in the ck-and-syntaxhighlighter WordPress plugin (versions <= 3.4.2) allows authenticated attackers to trick users into performing unintended actions that result in Stored XSS. Attackers can craft malicious requests that inject malicious scripts into the application, which are then executed when other users view the compromised content.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify ck-and-syntaxhighlighter plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and search for 'ck-and-syntaxhighlighter' or check the plugins directory /wp-content/plugins/ for a folder named 'ck-and-syntaxhighlighter'Affected if The plugin is present in the plugins directory or listed in WordPress admin plugins list
-
Check installed plugin versionIn WordPress admin, find the ck-and-syntaxhighlighter plugin in the Plugins list and note the version number displayed below the plugin name, or open the main plugin file (e.g., ck-and-syntaxhighlighter.php) and look for the 'Version' header in the file commentsAffected if Version is 3.4.2 or lower
-
Inspect plugin admin actions for nonce validationExamine the main plugin PHP file for functions handling form submissions or admin actions. Search for presence of 'wp_verify_nonce', 'check_admin_referer', or 'check_ajax_referer' in files that process user-submitted content or settings. If these nonce verification functions are absent around form handlers, the plugin may be vulnerableAffected if No nonce validation is found in the plugin code that handles state-changing actions
-
Check for suspicious stored content in plugin-related database entriesQuery the WordPress database (wp_posts table) for any posts/pages containing script tags, iframe tags, or javascript: URIs in the content field, particularly if created around the time the vulnerability might have been exploited. Search for patterns like '<script', '<iframe', 'onerror=', 'onload=' in post_contentAffected if Malicious script injections are found in post content that could represent exploitation of the Stored XSS via CSRF
If the ck-and-syntaxhighlighter plugin is installed with version 3.4.2 or lower and lacks proper nonce validation on its admin actions, the environment is affected by this CSRF-to-Stored-XSS vulnerability.
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 dataUpgrade to version 3.4.3 or later which contains the security fix. Additionally, implement anti-CSRF tokens (nonce validation) on all state-changing actions and apply proper output escaping/sanitization to prevent XSS.
- 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-2024-54407 — 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-2024-54407 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