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-12406: CWE-352 Cross-Site Request Forgery (CSRF) in awensley Project Honey Pot Spam Trap

0
Medium
VulnerabilityCVE-2025-12406cvecve-2025-12406cwe-352
Published: Tue Nov 18 2025 (11/18/2025, 08:27:37 UTC)
Source: CVE Database V5
Vendor/Project: awensley
Product: Project Honey Pot Spam Trap

Description

The Project Honey Pot Spam Trap plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0.1. This is due to missing or incorrect nonce validation on the printAdminPage() function. This makes it possible for unauthenticated attackers to update 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/18/2025, 08:56:25 UTC

Technical Analysis

CVE-2025-12406 identifies a Cross-Site Request Forgery (CSRF) vulnerability in the Project Honey Pot Spam Trap plugin for WordPress, affecting all versions up to and including 1.0.1. The root cause is the absence or improper implementation of nonce validation within the printAdminPage() function, which is responsible for rendering the administrative interface. Nonces are security tokens used to verify that requests originate from legitimate users and not from malicious third parties. Without proper nonce checks, attackers can craft malicious web requests that, when executed by an authenticated administrator (e.g., by clicking a link), cause unauthorized changes to plugin settings or injection of malicious scripts. This vulnerability does not require the attacker to have prior authentication but does require user interaction, specifically targeting administrators. The vulnerability impacts confidentiality and integrity by enabling unauthorized configuration changes and potential script injection, though it does not directly affect availability. The CVSS 3.1 base score is 6.1, reflecting medium severity with network attack vector, low attack complexity, no privileges required, user interaction needed, and scope changed due to potential impact beyond the vulnerable component. No patches or known exploits are currently available or reported. The vulnerability was published on November 18, 2025, and assigned by Wordfence. Given the widespread use of WordPress in Europe and the popularity of spam protection plugins, this vulnerability poses a tangible risk to affected sites.

Potential Impact

For European organizations, exploitation of this CSRF vulnerability could lead to unauthorized modification of spam trap plugin settings, potentially disabling or altering spam detection mechanisms. This could increase exposure to spam, phishing, or malware delivery through compromised or misconfigured defenses. Additionally, injected malicious scripts could facilitate further attacks such as session hijacking, data theft, or lateral movement within the network. The confidentiality of administrative credentials and sensitive configuration data is at risk, as is the integrity of the website's security posture. While availability is not directly impacted, the reputational damage and operational disruption from spam or malware incidents could be significant. Organizations relying on WordPress sites for customer engagement, e-commerce, or internal communications are particularly vulnerable. The requirement for administrator interaction means social engineering or phishing campaigns could be leveraged to trigger exploitation, increasing the threat surface. The absence of known exploits provides a window for proactive mitigation, but also means attackers may develop exploits in the future.

Mitigation Recommendations

European organizations should immediately audit their WordPress installations to identify the presence of the Project Honey Pot Spam Trap plugin, particularly versions up to 1.0.1. If found, they should upgrade to a patched version once available or temporarily disable the plugin to eliminate the attack vector. In the absence of an official patch, administrators can implement web application firewall (WAF) rules to detect and block suspicious POST requests targeting the plugin's administrative endpoints. Enforcing strict Content Security Policy (CSP) headers can help mitigate the impact of any injected scripts. Additionally, administrators should be trained to recognize and avoid phishing attempts that could trick them into clicking malicious links. Implementing multi-factor authentication (MFA) for WordPress admin accounts can reduce the risk of credential compromise. Regular backups and monitoring of plugin settings for unauthorized changes will aid in rapid detection and recovery. Finally, organizations should subscribe to vulnerability advisories for timely updates on patches or exploit developments.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-10-28T14:53:21.080Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 691c305835a0ab0a56270fff

Added to database: 11/18/2025, 8:37:44 AM

Last enriched: 11/18/2025, 8:56:25 AM

Last updated: 11/22/2025, 3:05:05 AM

Views: 12

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