CVE-2026-1398: CWE-352 Cross-Site Request Forgery (CSRF) in chrisnowak Change WP URL
The Change WP URL 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 on the 'change-wp-url' page. This makes it possible for unauthenticated attackers to change the WP Login URL 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-2026-1398 is a Cross-Site Request Forgery (CSRF) vulnerability identified in the Change WP URL plugin for WordPress, affecting all versions up to and including 1.0. The root cause is the absence or incorrect implementation of nonce validation on the 'change-wp-url' administrative page. Nonces are security tokens used to verify that requests originate from legitimate users and not from malicious third parties. Without proper nonce checks, an attacker can craft a malicious web request that, when an authenticated administrator visits or clicks a specially crafted link, triggers a change in the WordPress login URL. This change can disrupt normal administrative access or be leveraged as part of a broader attack chain. The vulnerability requires no prior authentication but does require user interaction from an administrator, such as clicking a link or visiting a malicious page. The CVSS 3.1 base score is 4.3, reflecting a network attack vector, low attack complexity, no privileges required, but requiring user interaction, and impacting integrity only (changing configuration). There are no known exploits in the wild at the time of publication, and no official patches have been released yet. The plugin is developed by chrisnowak and is used to customize the WordPress login URL, a common security hardening technique. The vulnerability could be exploited to undermine such hardening by reverting or redirecting the login URL, potentially exposing the site to brute force or other attacks if combined with other vulnerabilities.
Potential Impact
For European organizations, this vulnerability primarily threatens the integrity of WordPress site configurations. By changing the login URL without authorization, attackers can disrupt administrator access or bypass security through obscurity measures. This could lead to increased risk of further compromise if attackers combine this with credential stuffing or brute force attacks on the default or changed login URLs. While confidentiality and availability are not directly impacted, the altered login URL can cause administrative delays and potential downtime if administrators cannot access the site. Organizations relying heavily on WordPress for public-facing websites, e-commerce, or internal portals may face operational disruptions. The risk is heightened in environments where administrators frequently access the WordPress dashboard and may be susceptible to phishing or social engineering attacks that trick them into clicking malicious links. Given the lack of patches, the window of exposure remains until mitigations or updates are applied.
Mitigation Recommendations
1. Restrict administrative access to trusted networks and IP addresses to reduce exposure to CSRF attacks. 2. Implement web application firewalls (WAFs) with rules to detect and block suspicious POST requests targeting the 'change-wp-url' endpoint. 3. Educate WordPress administrators about phishing and social engineering risks to prevent inadvertent clicks on malicious links. 4. Regularly monitor WordPress configuration changes and login URL settings to detect unauthorized modifications promptly. 5. Use multi-factor authentication (MFA) for WordPress admin accounts to mitigate the impact of compromised credentials. 6. Until an official patch is released, consider temporarily disabling or removing the Change WP URL plugin if feasible. 7. Follow the plugin vendor’s updates closely and apply security patches immediately upon release. 8. Employ security plugins that add additional CSRF protections or nonce validations as a temporary workaround. 9. Conduct regular security audits and vulnerability scans to identify and remediate similar issues proactively.
Affected Countries
Germany, United Kingdom, France, Netherlands, Italy, Spain
CVE-2026-1398: CWE-352 Cross-Site Request Forgery (CSRF) in chrisnowak Change WP URL
Description
The Change WP URL 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 on the 'change-wp-url' page. This makes it possible for unauthenticated attackers to change the WP Login URL via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
AI-Powered Analysis
Technical Analysis
CVE-2026-1398 is a Cross-Site Request Forgery (CSRF) vulnerability identified in the Change WP URL plugin for WordPress, affecting all versions up to and including 1.0. The root cause is the absence or incorrect implementation of nonce validation on the 'change-wp-url' administrative page. Nonces are security tokens used to verify that requests originate from legitimate users and not from malicious third parties. Without proper nonce checks, an attacker can craft a malicious web request that, when an authenticated administrator visits or clicks a specially crafted link, triggers a change in the WordPress login URL. This change can disrupt normal administrative access or be leveraged as part of a broader attack chain. The vulnerability requires no prior authentication but does require user interaction from an administrator, such as clicking a link or visiting a malicious page. The CVSS 3.1 base score is 4.3, reflecting a network attack vector, low attack complexity, no privileges required, but requiring user interaction, and impacting integrity only (changing configuration). There are no known exploits in the wild at the time of publication, and no official patches have been released yet. The plugin is developed by chrisnowak and is used to customize the WordPress login URL, a common security hardening technique. The vulnerability could be exploited to undermine such hardening by reverting or redirecting the login URL, potentially exposing the site to brute force or other attacks if combined with other vulnerabilities.
Potential Impact
For European organizations, this vulnerability primarily threatens the integrity of WordPress site configurations. By changing the login URL without authorization, attackers can disrupt administrator access or bypass security through obscurity measures. This could lead to increased risk of further compromise if attackers combine this with credential stuffing or brute force attacks on the default or changed login URLs. While confidentiality and availability are not directly impacted, the altered login URL can cause administrative delays and potential downtime if administrators cannot access the site. Organizations relying heavily on WordPress for public-facing websites, e-commerce, or internal portals may face operational disruptions. The risk is heightened in environments where administrators frequently access the WordPress dashboard and may be susceptible to phishing or social engineering attacks that trick them into clicking malicious links. Given the lack of patches, the window of exposure remains until mitigations or updates are applied.
Mitigation Recommendations
1. Restrict administrative access to trusted networks and IP addresses to reduce exposure to CSRF attacks. 2. Implement web application firewalls (WAFs) with rules to detect and block suspicious POST requests targeting the 'change-wp-url' endpoint. 3. Educate WordPress administrators about phishing and social engineering risks to prevent inadvertent clicks on malicious links. 4. Regularly monitor WordPress configuration changes and login URL settings to detect unauthorized modifications promptly. 5. Use multi-factor authentication (MFA) for WordPress admin accounts to mitigate the impact of compromised credentials. 6. Until an official patch is released, consider temporarily disabling or removing the Change WP URL plugin if feasible. 7. Follow the plugin vendor’s updates closely and apply security patches immediately upon release. 8. Employ security plugins that add additional CSRF protections or nonce validations as a temporary workaround. 9. Conduct regular security audits and vulnerability scans to identify and remediate similar issues proactively.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-01-23T21:32:03.372Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6979f49e4623b1157cb36555
Added to database: 1/28/2026, 11:35:58 AM
Last enriched: 1/28/2026, 11:51:28 AM
Last updated: 2/4/2026, 11:12:38 AM
Views: 20
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.
Related Threats
CVE-2025-59818: Vulnerability in Zenitel TCIS-3+
CriticalCVE-2025-41085: CWE-79 Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') in Apidog Apidog Web Platform
MediumDetecting and Monitoring OpenClaw (clawdbot, moltbot), (Tue, Feb 3rd)
MediumMalicious Script Delivering More Maliciousness, (Wed, Feb 4th)
MediumEclipse Foundation Mandates Pre-Publish Security Checks for Open VSX Extensions
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.