CVE-2025-12069: CWE-352 Cross-Site Request Forgery (CSRF) in stiand WP Global Screen Options
The WP Global Screen Options plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 0.2. This is due to missing nonce validation on the `updatewpglobalscreenoptions` action handler. This makes it possible for unauthenticated attackers to modify global screen options for all users via a forged request granted they can trick an administrator into performing an action such as clicking on a link.
AI Analysis
Technical Summary
CVE-2025-12069 is a Cross-Site Request Forgery (CSRF) vulnerability identified in the WP Global Screen Options plugin for WordPress, maintained by stiand. This vulnerability affects all versions up to and including 0.2 due to the absence of nonce validation on the updatewpglobalscreenoptions action handler. Nonce validation is a security mechanism used in WordPress to verify that requests are intentional and originate from legitimate users. Without this protection, an attacker can craft a malicious request that, if an administrator clicks on a specially crafted link or visits a malicious webpage, will execute actions on behalf of the administrator without their consent. Specifically, the attacker can modify global screen options that affect all users, potentially altering the administrative interface or user experience. The vulnerability does not require authentication, but it does require user interaction (an administrator must be tricked into clicking the malicious link). The CVSS 3.1 base score is 4.3, indicating a medium severity primarily due to the limited impact on integrity and no impact on confidentiality or availability. No known exploits have been reported in the wild, and no patches have been released at the time of publication. This vulnerability falls under CWE-352, which covers CSRF weaknesses. The plugin's widespread use in WordPress environments makes this a relevant threat for administrators managing affected sites.
Potential Impact
The primary impact of this vulnerability is the unauthorized modification of global screen options across all users of a WordPress site using the vulnerable plugin. While this does not directly compromise sensitive data confidentiality or availability, it undermines the integrity of the administrative interface and user experience. Attackers could potentially use this to confuse administrators, disrupt workflows, or prepare the environment for further attacks by altering interface settings. Since the vulnerability requires an administrator to be tricked into clicking a malicious link, the attack vector depends on successful social engineering. Organizations relying on this plugin risk administrative disruption and potential escalation if attackers leverage the altered settings to facilitate additional exploits. The impact is more significant for high-profile or large-scale WordPress deployments where administrative control is critical. However, the absence of known exploits and the medium CVSS score suggest the threat is moderate but should not be ignored.
Mitigation Recommendations
1. Immediately restrict administrative access to trusted personnel and enforce the principle of least privilege to minimize exposure. 2. Educate administrators about the risks of clicking untrusted links and implement security awareness training focused on phishing and social engineering. 3. Monitor HTTP requests to the updatewpglobalscreenoptions action handler for unusual or unauthorized activity, using web application firewalls (WAF) or intrusion detection systems (IDS). 4. Temporarily disable or remove the WP Global Screen Options plugin if it is not essential to reduce the attack surface until a patch is released. 5. Follow the plugin vendor and WordPress security advisories closely and apply updates or patches as soon as they become available. 6. Implement Content Security Policy (CSP) headers and SameSite cookies to reduce the risk of CSRF attacks. 7. Consider deploying additional nonce validation or custom CSRF protections if feasible within the plugin or site codebase. 8. Regularly audit user roles and permissions to ensure no excessive privileges are granted.
Affected Countries
United States, Germany, United Kingdom, Canada, Australia, France, Netherlands, India, Brazil, Japan
CVE-2025-12069: CWE-352 Cross-Site Request Forgery (CSRF) in stiand WP Global Screen Options
Description
The WP Global Screen Options plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 0.2. This is due to missing nonce validation on the `updatewpglobalscreenoptions` action handler. This makes it possible for unauthenticated attackers to modify global screen options for all users via a forged request granted they can trick an administrator into performing an action such as clicking on a link.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2025-12069 is a Cross-Site Request Forgery (CSRF) vulnerability identified in the WP Global Screen Options plugin for WordPress, maintained by stiand. This vulnerability affects all versions up to and including 0.2 due to the absence of nonce validation on the updatewpglobalscreenoptions action handler. Nonce validation is a security mechanism used in WordPress to verify that requests are intentional and originate from legitimate users. Without this protection, an attacker can craft a malicious request that, if an administrator clicks on a specially crafted link or visits a malicious webpage, will execute actions on behalf of the administrator without their consent. Specifically, the attacker can modify global screen options that affect all users, potentially altering the administrative interface or user experience. The vulnerability does not require authentication, but it does require user interaction (an administrator must be tricked into clicking the malicious link). The CVSS 3.1 base score is 4.3, indicating a medium severity primarily due to the limited impact on integrity and no impact on confidentiality or availability. No known exploits have been reported in the wild, and no patches have been released at the time of publication. This vulnerability falls under CWE-352, which covers CSRF weaknesses. The plugin's widespread use in WordPress environments makes this a relevant threat for administrators managing affected sites.
Potential Impact
The primary impact of this vulnerability is the unauthorized modification of global screen options across all users of a WordPress site using the vulnerable plugin. While this does not directly compromise sensitive data confidentiality or availability, it undermines the integrity of the administrative interface and user experience. Attackers could potentially use this to confuse administrators, disrupt workflows, or prepare the environment for further attacks by altering interface settings. Since the vulnerability requires an administrator to be tricked into clicking a malicious link, the attack vector depends on successful social engineering. Organizations relying on this plugin risk administrative disruption and potential escalation if attackers leverage the altered settings to facilitate additional exploits. The impact is more significant for high-profile or large-scale WordPress deployments where administrative control is critical. However, the absence of known exploits and the medium CVSS score suggest the threat is moderate but should not be ignored.
Mitigation Recommendations
1. Immediately restrict administrative access to trusted personnel and enforce the principle of least privilege to minimize exposure. 2. Educate administrators about the risks of clicking untrusted links and implement security awareness training focused on phishing and social engineering. 3. Monitor HTTP requests to the updatewpglobalscreenoptions action handler for unusual or unauthorized activity, using web application firewalls (WAF) or intrusion detection systems (IDS). 4. Temporarily disable or remove the WP Global Screen Options plugin if it is not essential to reduce the attack surface until a patch is released. 5. Follow the plugin vendor and WordPress security advisories closely and apply updates or patches as soon as they become available. 6. Implement Content Security Policy (CSP) headers and SameSite cookies to reduce the risk of CSRF attacks. 7. Consider deploying additional nonce validation or custom CSRF protections if feasible within the plugin or site codebase. 8. Regularly audit user roles and permissions to ensure no excessive privileges are granted.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-10-22T13:54:39.633Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 690977bf78d4f574c2b12d20
Added to database: 11/4/2025, 3:49:19 AM
Last enriched: 2/27/2026, 7:58:42 PM
Last updated: 3/25/2026, 2:20:28 PM
Views: 53
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.