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

CVE-2025-12413

MEDIUM · 5.4 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 →
61/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 Social Media WPCF7 Stop Words plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.1.3. This is due to missing or incorrect nonce validation on the smWpCfSwOptions() 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 · high confidence

The Social Media WPCF7 Stop Words WordPress plugin fails to validate nonces in its smWpCfSwOptions() function, allowing unauthenticated attackers to forge administrative requests. This enables modification of plugin settings and injection of malicious web scripts via social engineering of site administrators.

MitigationUpdate to a patched version when released; alternatively disable the plugin. Adminstrators should avoid clicking untrusted links to prevent CSRF attacks.

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 checks

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

  1. Identify if the Social Media WPCF7 Stop Words plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'social-media-wpcf7-stop-words' or similar. Alternatively, query the wp_options table for option_name = 'active_plugins' and check if the plugin is listed.
    Affected if The plugin folder exists in the plugins directory or the plugin is listed in active_plugins.
  2. Locate the plugin main file to check version
    Find the main plugin file in the plugin directory (typically named index.php, main.php, or social-media-wpcf7-stop-words.php) and read the plugin header for the Version field.
    Affected if The plugin is present but the version cannot be confirmed as patched.
  3. Verify the smWpCfSwOptions function exists
    Search the plugin source code for the function 'smWpCfSwOptions' and examine if it includes nonce verification using functions like wp_verify_nonce or check_admin_referer.
    Affected if The function exists and does NOT validate nonces (missing wp_verify_nonce or check_admin_referer calls).
  4. Confirm the plugin is active on the site
    Check WordPress admin under Plugins > Installed Plugins, or query the wp_options table for active_plugins option.
    Affected if The plugin is currently activated.
  5. Review admin action hooks used by the plugin
    Examine the plugin code for admin action hooks (admin_post_, wp_ajax_, or add_menu_page) that call smWpCfSwOptions without nonce validation.
    Affected if The plugin handles admin requests without nonce verification.

If the Social Media WPCF7 Stop Words plugin is installed, active, and its smWpCfSwOptions() function lacks nonce validation, the site is vulnerable to CVE-2025-12413 CSRF attacks.

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 to a patched version when released; alternatively disable the plugin. Adminstrators should avoid clicking untrusted links to prevent CSRF attacks.

Recommended fix Moderate confidence

Latest version beyond 1.1.3 (check WordPress Plugin Repository for current release)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Social Media WPCF7 Stop Words plugin
  4. Check if an update is available and install the latest version
  5. If no update appears in WordPress, manually download the latest version from the WordPress Plugin Repository at plugins.trac.wordpress.org and reinstall

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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