CVE-2025-68082
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 SEMrush CY LTD Semrush Content Toolkit semrush-contentshake allows Cross Site Request Forgery.This issue affects Semrush Content Toolkit: from n/a through <= 1.1.32.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the Semrush Content Toolkit (semrush-contentshake) WordPress plugin allows remote attackers to trick authenticated users into performing unintended actions by forging requests. The vulnerability exists in versions up to and including 1.1.32, likely due to missing or improper anti-CSRF token validation on state-changing operations.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Semrush Content Toolkit plugin is installedCheck if the semrush-contentshake directory exists in wp-content/plugins/ on the WordPress filesystemAffected if The plugin directory semrush-contentshake exists in the plugins folder
-
Determine installed plugin versionOpen the main plugin file (usually semrush-contentshake.php) and locate the Version header in the plugin comment block, or read version from readme.txtAffected if The reported version is 1.1.32 or lower (any version up to and including 1.1.32)
-
Identify state-changing operations in the pluginSearch the plugin source code for form tags, AJAX action handlers (wp_ajax_*), admin-post.php submissions, and any functions that modify data or settingsAffected if The plugin contains form submissions or data modification functions without visible nonce verification
-
Inspect code for anti-CSRF nonce validationSearch the plugin PHP files for wp_verify_nonce, check_admin_referer, wp_create_nonce, or nonce_field function calls near state-changing operationsAffected if State-changing operations lack wp_verify_nonce or check_admin_referer calls, or nonces are not verified before executing actions
-
Check for Origin and Referer header validationSearch the plugin for $_SERVER['HTTP_ORIGIN'], $_SERVER['HTTP_REFERER'] validation, or server-side origin checking before processing requestsAffected if The plugin does not validate Origin or Referer headers for cross-origin requests
If the Semrush Content Toolkit plugin version is 1.1.32 or lower and state-changing operations lack nonce verification, the environment is vulnerable to CSRF attacks.
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 dataImplement anti-CSRF tokens (nonces) for all state-changing operations, validate the Origin and Referer headers server-side, and set SameSite attribute on session cookies to prevent cross-site request forgery attacks.
- 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-2025-68082 — 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-2025-68082 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