CVE-2022-3489: CWE-862 Missing Authorization in Unknown Wp-Hide
The WP Hide WordPress plugin through 0.0.2 does not have authorisation and CSRF checks in place when updating the custom_wpadmin_slug settings, allowing unauthenticated attackers to update it with a crafted request
AI Analysis
Technical Summary
CVE-2022-3489 is a medium-severity vulnerability affecting version 0.0.2 of the WP Hide WordPress plugin. This plugin is designed to obscure or change default WordPress paths to enhance security by hiding common WordPress endpoints. The vulnerability arises due to missing authorization and Cross-Site Request Forgery (CSRF) protections when updating the 'custom_wpadmin_slug' setting. Specifically, the plugin does not verify whether the request to change this critical setting is coming from an authenticated and authorized user, nor does it implement CSRF tokens to prevent unauthorized state-changing requests. As a result, an unauthenticated attacker can craft and send a malicious HTTP request to update the 'custom_wpadmin_slug' parameter. This setting controls the URL slug for the WordPress admin login page, and unauthorized modification can redirect legitimate users to attacker-controlled endpoints or disrupt administrative access. The vulnerability is exploitable remotely without any authentication or user interaction, as indicated by the CVSS vector (AV:N/AC:L/PR:N/UI:N). The impact is limited to integrity, as the attacker can alter configuration settings but cannot directly compromise confidentiality or availability. No known exploits have been reported in the wild, and no official patches or updates have been linked, implying that mitigation relies on plugin updates or manual intervention. The vulnerability is categorized under CWE-862 (Missing Authorization) and CWE-352 (Cross-Site Request Forgery), highlighting the absence of proper access control and CSRF protections in the plugin's update mechanism.
Potential Impact
For European organizations using the WP Hide plugin version 0.0.2, this vulnerability poses a risk primarily to the integrity of their WordPress administrative interface. Unauthorized modification of the admin login slug can lead to administrative lockout, redirection to malicious pages, or facilitate further attacks such as phishing or credential harvesting. While the vulnerability does not directly expose sensitive data or cause denial of service, the alteration of admin paths can undermine security controls and complicate incident response. Organizations relying on WordPress for public-facing websites, e-commerce, or internal portals may experience reputational damage and operational disruption if attackers exploit this flaw to manipulate admin access. Given the ease of exploitation (no authentication or user interaction required), automated scanning and exploitation attempts could increase if the vulnerability becomes widely known. However, the absence of known exploits in the wild suggests limited current impact. The threat is more significant for organizations with limited patch management processes or those using outdated plugin versions without monitoring for security updates.
Mitigation Recommendations
1. Immediate upgrade: Organizations should verify the WP Hide plugin version and upgrade to a patched or newer version if available. If no official patch exists, consider disabling or uninstalling the plugin until a fix is released. 2. Access control: Restrict administrative access to WordPress dashboards via IP whitelisting or VPN to reduce exposure to unauthenticated requests. 3. Web application firewall (WAF): Deploy WAF rules to detect and block unauthorized attempts to modify the 'custom_wpadmin_slug' parameter or suspicious POST requests targeting the plugin endpoints. 4. Monitor logs: Enable detailed logging of HTTP requests to WordPress admin endpoints and monitor for unusual or unauthorized changes to configuration parameters. 5. Implement CSRF protections: If maintaining a custom or forked version of the plugin, ensure that all state-changing requests include proper authorization checks and CSRF tokens. 6. Incident response readiness: Prepare to restore admin access via database-level interventions if the admin slug is maliciously changed, including knowledge of how to reset or override the slug directly in the WordPress database. 7. User awareness: Educate administrators about the risks of using outdated plugins and the importance of timely updates and security hygiene.
Affected Countries
Germany, United Kingdom, France, Netherlands, Italy, Spain, Poland, Sweden
CVE-2022-3489: CWE-862 Missing Authorization in Unknown Wp-Hide
Description
The WP Hide WordPress plugin through 0.0.2 does not have authorisation and CSRF checks in place when updating the custom_wpadmin_slug settings, allowing unauthenticated attackers to update it with a crafted request
AI-Powered Analysis
Technical Analysis
CVE-2022-3489 is a medium-severity vulnerability affecting version 0.0.2 of the WP Hide WordPress plugin. This plugin is designed to obscure or change default WordPress paths to enhance security by hiding common WordPress endpoints. The vulnerability arises due to missing authorization and Cross-Site Request Forgery (CSRF) protections when updating the 'custom_wpadmin_slug' setting. Specifically, the plugin does not verify whether the request to change this critical setting is coming from an authenticated and authorized user, nor does it implement CSRF tokens to prevent unauthorized state-changing requests. As a result, an unauthenticated attacker can craft and send a malicious HTTP request to update the 'custom_wpadmin_slug' parameter. This setting controls the URL slug for the WordPress admin login page, and unauthorized modification can redirect legitimate users to attacker-controlled endpoints or disrupt administrative access. The vulnerability is exploitable remotely without any authentication or user interaction, as indicated by the CVSS vector (AV:N/AC:L/PR:N/UI:N). The impact is limited to integrity, as the attacker can alter configuration settings but cannot directly compromise confidentiality or availability. No known exploits have been reported in the wild, and no official patches or updates have been linked, implying that mitigation relies on plugin updates or manual intervention. The vulnerability is categorized under CWE-862 (Missing Authorization) and CWE-352 (Cross-Site Request Forgery), highlighting the absence of proper access control and CSRF protections in the plugin's update mechanism.
Potential Impact
For European organizations using the WP Hide plugin version 0.0.2, this vulnerability poses a risk primarily to the integrity of their WordPress administrative interface. Unauthorized modification of the admin login slug can lead to administrative lockout, redirection to malicious pages, or facilitate further attacks such as phishing or credential harvesting. While the vulnerability does not directly expose sensitive data or cause denial of service, the alteration of admin paths can undermine security controls and complicate incident response. Organizations relying on WordPress for public-facing websites, e-commerce, or internal portals may experience reputational damage and operational disruption if attackers exploit this flaw to manipulate admin access. Given the ease of exploitation (no authentication or user interaction required), automated scanning and exploitation attempts could increase if the vulnerability becomes widely known. However, the absence of known exploits in the wild suggests limited current impact. The threat is more significant for organizations with limited patch management processes or those using outdated plugin versions without monitoring for security updates.
Mitigation Recommendations
1. Immediate upgrade: Organizations should verify the WP Hide plugin version and upgrade to a patched or newer version if available. If no official patch exists, consider disabling or uninstalling the plugin until a fix is released. 2. Access control: Restrict administrative access to WordPress dashboards via IP whitelisting or VPN to reduce exposure to unauthenticated requests. 3. Web application firewall (WAF): Deploy WAF rules to detect and block unauthorized attempts to modify the 'custom_wpadmin_slug' parameter or suspicious POST requests targeting the plugin endpoints. 4. Monitor logs: Enable detailed logging of HTTP requests to WordPress admin endpoints and monitor for unusual or unauthorized changes to configuration parameters. 5. Implement CSRF protections: If maintaining a custom or forked version of the plugin, ensure that all state-changing requests include proper authorization checks and CSRF tokens. 6. Incident response readiness: Prepare to restore admin access via database-level interventions if the admin slug is maliciously changed, including knowledge of how to reset or override the slug directly in the WordPress database. 7. User awareness: Educate administrators about the risks of using outdated plugins and the importance of timely updates and security hygiene.
Affected Countries
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- WPScan
- Date Reserved
- 2022-10-13T00:00:00.000Z
- Cisa Enriched
- true
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 682d9838c4522896dcbec444
Added to database: 5/21/2025, 9:09:12 AM
Last enriched: 6/25/2025, 11:01:11 PM
Last updated: 2/2/2026, 5:06:11 PM
Views: 47
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-2026-0921
UnknownCVE-2026-1232: CWE-693 in BeyondTrust Privilege management for Windows
MediumCVE-2025-47402: CWE-126 Buffer Over-read in Qualcomm, Inc. Snapdragon
MediumCVE-2025-47399: CWE-120 Buffer Copy Without Checking Size of Input ('Classic Buffer Overflow') in Qualcomm, Inc. Snapdragon
HighCVE-2025-47398: CWE-416 Use After Free in Qualcomm, Inc. Snapdragon
HighActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
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.