CVE-2025-9887: CWE-352 Cross-Site Request Forgery (CSRF) in bittokazi Custom Login And Signup Widget
The Custom Login And Signup Widget plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0. This is due to missing or incorrect nonce validation in the /frndzk_adminclsw.php file. This makes it possible for unauthenticated attackers to change the email and username settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
AI Analysis
Technical Summary
CVE-2025-9887 identifies a Cross-Site Request Forgery (CSRF) vulnerability in the Custom Login And Signup Widget plugin developed by bittokazi for WordPress. The flaw exists due to missing or incorrect nonce validation in the /frndzk_adminclsw.php file, which is responsible for handling administrative actions related to user login and signup settings. Nonces are security tokens used to verify that requests originate from legitimate users and not from malicious third-party sites. Without proper nonce validation, an attacker can craft a malicious request that, when executed by an authenticated administrator (e.g., by clicking a link), changes critical user account settings such as email addresses and usernames. This attack does not require the attacker to be authenticated themselves but does require user interaction from a privileged user. The vulnerability affects all versions up to 1.0 of the plugin. The CVSS 3.1 base score of 4.3 reflects that the attack vector is network-based, requires no privileges, but does require user interaction, and impacts integrity but not confidentiality or availability. No patches or exploit code are currently publicly available, and no active exploitation has been reported. However, the vulnerability poses a risk to the integrity of user account data and could facilitate further attacks if exploited.
Potential Impact
The primary impact of this vulnerability is the unauthorized modification of user account settings, specifically email and username fields, by an attacker leveraging CSRF. This can lead to account takeover scenarios if attackers change email addresses to ones they control, enabling password reset or other account recovery mechanisms. Although confidentiality and availability are not directly affected, the integrity compromise can undermine trust in the affected WordPress site and its user management. For organizations, this could result in unauthorized access, potential privilege escalation, and disruption of user authentication workflows. The requirement for administrator interaction limits the ease of exploitation but does not eliminate risk, especially in environments with many administrators or where phishing is feasible. The lack of known exploits reduces immediate threat but does not preclude future attacks. Organizations relying on this plugin for user management face reputational damage, potential data integrity issues, and increased risk of further compromise if attackers leverage changed credentials.
Mitigation Recommendations
To mitigate this vulnerability, organizations should first check for plugin updates or patches from the vendor and apply them promptly once available. In the absence of an official patch, administrators can implement the following specific measures: 1) Disable or remove the Custom Login And Signup Widget plugin if it is not essential to reduce attack surface. 2) Implement Web Application Firewall (WAF) rules to detect and block suspicious POST requests targeting /frndzk_adminclsw.php, especially those lacking valid nonce tokens or originating from external referrers. 3) Educate administrators about phishing and social engineering risks to prevent clicking on untrusted links. 4) Restrict administrative access to trusted networks or VPNs to reduce exposure. 5) Monitor logs for unusual changes to user account settings and implement alerting for such events. 6) Consider adding custom nonce validation or CSRF protections if feasible by modifying plugin code or using security plugins that enforce nonce checks. These targeted mitigations go beyond generic advice by focusing on the specific vulnerable endpoint and attack vector.
Affected Countries
United States, Germany, India, Brazil, United Kingdom, Canada, Australia, France, Netherlands, Japan
CVE-2025-9887: CWE-352 Cross-Site Request Forgery (CSRF) in bittokazi Custom Login And Signup Widget
Description
The Custom Login And Signup Widget plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0. This is due to missing or incorrect nonce validation in the /frndzk_adminclsw.php file. This makes it possible for unauthenticated attackers to change the email and username settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2025-9887 identifies a Cross-Site Request Forgery (CSRF) vulnerability in the Custom Login And Signup Widget plugin developed by bittokazi for WordPress. The flaw exists due to missing or incorrect nonce validation in the /frndzk_adminclsw.php file, which is responsible for handling administrative actions related to user login and signup settings. Nonces are security tokens used to verify that requests originate from legitimate users and not from malicious third-party sites. Without proper nonce validation, an attacker can craft a malicious request that, when executed by an authenticated administrator (e.g., by clicking a link), changes critical user account settings such as email addresses and usernames. This attack does not require the attacker to be authenticated themselves but does require user interaction from a privileged user. The vulnerability affects all versions up to 1.0 of the plugin. The CVSS 3.1 base score of 4.3 reflects that the attack vector is network-based, requires no privileges, but does require user interaction, and impacts integrity but not confidentiality or availability. No patches or exploit code are currently publicly available, and no active exploitation has been reported. However, the vulnerability poses a risk to the integrity of user account data and could facilitate further attacks if exploited.
Potential Impact
The primary impact of this vulnerability is the unauthorized modification of user account settings, specifically email and username fields, by an attacker leveraging CSRF. This can lead to account takeover scenarios if attackers change email addresses to ones they control, enabling password reset or other account recovery mechanisms. Although confidentiality and availability are not directly affected, the integrity compromise can undermine trust in the affected WordPress site and its user management. For organizations, this could result in unauthorized access, potential privilege escalation, and disruption of user authentication workflows. The requirement for administrator interaction limits the ease of exploitation but does not eliminate risk, especially in environments with many administrators or where phishing is feasible. The lack of known exploits reduces immediate threat but does not preclude future attacks. Organizations relying on this plugin for user management face reputational damage, potential data integrity issues, and increased risk of further compromise if attackers leverage changed credentials.
Mitigation Recommendations
To mitigate this vulnerability, organizations should first check for plugin updates or patches from the vendor and apply them promptly once available. In the absence of an official patch, administrators can implement the following specific measures: 1) Disable or remove the Custom Login And Signup Widget plugin if it is not essential to reduce attack surface. 2) Implement Web Application Firewall (WAF) rules to detect and block suspicious POST requests targeting /frndzk_adminclsw.php, especially those lacking valid nonce tokens or originating from external referrers. 3) Educate administrators about phishing and social engineering risks to prevent clicking on untrusted links. 4) Restrict administrative access to trusted networks or VPNs to reduce exposure. 5) Monitor logs for unusual changes to user account settings and implement alerting for such events. 6) Consider adding custom nonce validation or CSRF protections if feasible by modifying plugin code or using security plugins that enforce nonce checks. These targeted mitigations go beyond generic advice by focusing on the specific vulnerable endpoint and attack vector.
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-09-02T22:24:44.959Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 68ce4e4eab7f779c79ff312b
Added to database: 9/20/2025, 6:48:46 AM
Last enriched: 2/26/2026, 6:19:28 PM
Last updated: 3/23/2026, 12:58:47 PM
Views: 170
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.