dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-12410

MEDIUM · 6.1 CVSS v3.1 Published 2025-11-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
The SH Contextual Help plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.2.1. This is due to missing or incorrect nonce validation in the sh_contextual_help_dashboard_widget() function. This makes it possible for unauthenticated attackers to update the plugin's settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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

The SH Contextual Help WordPress plugin versions up to 3.2.1 contain a Cross-Site Request Forgery (CSRF) vulnerability in the sh_contextual_help_dashboard_widget() function due to missing or incorrect nonce validation. This allows unauthenticated attackers to forge administrative requests that can modify plugin settings and inject malicious web scripts, provided they can socially engineer a site administrator into clicking a crafted link.

MitigationUpdate the plugin to the latest version once a patch is released, or disable the plugin until a fix is available. Until patched, administrators should be vigilant about clicking unknown links.

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
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. Confirm SH Contextual Help plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'SH Contextual Help' or check the wp-content/plugins directory for a folder named 'sh-contextual-help' or similar
    Affected if The plugin is present in the WordPress installation
  2. Check installed plugin version
    In WordPress admin, click on the plugin from the Plugins page to view its details, or inspect the plugin's main PHP file header for the 'Version' comment tag
    Affected if The version is 3.2.1 or lower
  3. Locate the vulnerable function in the codebase
    Search the plugin files for the function 'sh_contextual_help_dashboard_widget' - typically in the main plugin PHP file or a dashboard-related file
    Affected if The function exists in the plugin code
  4. Verify absence of nonce validation in the affected function
    Examine the sh_contextual_help_dashboard_widget function code and look for WordPress nonce verification calls such as wp_verify_nonce, check_admin_referer, or wp_nonce_field within or before this function handles form submissions
    Affected if No nonce verification is found before the function processes requests or modifies settings

A user is affected if the SH Contextual Help plugin is installed with version 3.2.1 or lower and the dashboard widget function lacks proper nonce validation, allowing forged administrative requests to modify settings or inject scripts.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to the latest version once a patch is released, or disable the plugin until a fix is available. Until patched, administrators should be vigilant about clicking unknown links.

Recommended fix Moderate confidence

Version 3.2.2 or later (upgrade to latest available version)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'SH Contextual Help' plugin
  4. Check the current version (should be 3.2.1 or below)
  5. Update the plugin to the latest available version which contains the security fix

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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