Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-12413: CWE-352 Cross-Site Request Forgery (CSRF) in socialmedialtd WPCF7 Stop words

0
Medium
VulnerabilityCVE-2025-12413cvecve-2025-12413cwe-352
Published: Tue Nov 04 2025 (11/04/2025, 04:27:14 UTC)
Source: CVE Database V5
Vendor/Project: socialmedialtd
Product: WPCF7 Stop words

Description

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.

AI-Powered Analysis

AILast updated: 11/11/2025, 08:19:37 UTC

Technical Analysis

CVE-2025-12413 identifies a Cross-Site Request Forgery (CSRF) vulnerability in the Social Media WPCF7 Stop Words plugin for WordPress, affecting all versions up to and including 1.1.3. The vulnerability stems from the smWpCfSwOptions() function lacking proper nonce validation, which is a security token mechanism designed to prevent unauthorized commands from being executed. Without this validation, attackers can craft malicious requests that, when an authenticated site administrator interacts with them (e.g., by clicking a link), cause the plugin's settings to be updated without consent. This can lead to the injection of malicious web scripts, potentially enabling further attacks such as persistent cross-site scripting (XSS) or site defacement. The vulnerability does not require the attacker to be authenticated but does require user interaction from an administrator, making social engineering a key component of exploitation. The CVSS 3.1 base score is 5.4 (medium), reflecting network attack vector, low attack complexity, no privileges required, but user interaction needed, with impact primarily on integrity and availability but not confidentiality. No patches or known exploits are currently reported, but the risk remains significant due to the potential for site compromise and disruption. The plugin is used in WordPress environments, which are widely deployed across many European organizations for content management and online presence.

Potential Impact

For European organizations, exploitation of this vulnerability could lead to unauthorized changes in plugin configurations and injection of malicious scripts, undermining website integrity and availability. This can result in defacement, disruption of services, or further compromise through chained attacks such as persistent XSS or malware distribution. Organizations relying on WordPress for critical business functions or customer engagement may suffer reputational damage, loss of user trust, and potential regulatory scrutiny under GDPR if user data is indirectly affected. The requirement for administrator interaction means that phishing or social engineering campaigns targeting site admins could be a vector, increasing the risk in environments with less stringent security awareness. The medium severity score indicates a moderate risk but one that should not be ignored, especially for organizations with public-facing WordPress sites using the vulnerable plugin.

Mitigation Recommendations

1. Monitor for and apply any official patches or updates from the plugin vendor as soon as they become available. 2. Until patches are released, consider disabling or uninstalling the Social Media WPCF7 Stop Words plugin to eliminate the attack surface. 3. Implement strict access controls and multi-factor authentication (MFA) for WordPress administrator accounts to reduce the risk of successful social engineering. 4. Educate administrators about the risks of clicking on unsolicited or suspicious links, especially those that could trigger administrative actions. 5. Employ web application firewalls (WAFs) with rules designed to detect and block CSRF attack patterns targeting WordPress admin endpoints. 6. Regularly audit plugin configurations and logs for unauthorized changes or suspicious activity. 7. Use security plugins that enforce nonce validation and other best practices to harden WordPress installations. 8. Segment administrative interfaces and restrict access by IP or VPN where feasible to limit exposure.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-10-28T15:38:24.764Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 690984df2b77ca42b4883f42

Added to database: 11/4/2025, 4:45:19 AM

Last enriched: 11/11/2025, 8:19:37 AM

Last updated: 12/20/2025, 5:17:40 PM

Views: 44

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats