Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify site running Easy Hide Login
-
DeliverySend crafted password-reset request
-
ExploitReach standard login page
-
ExecutionParse secret login slug from response
-
ImpactTarget login form for credential attacks
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The target must be running the Easy Hide Login WordPress plugin at a version before 1.7 with its hidden-login (custom secret slug) protection active - this is the plugin's core and default feature, so any site using the plugin for its intended purpose is exposed. Exploitation is remote and unauthenticated (AV:N/PR:N/UI:N) with no special configuration beyond having the plugin enabled; the attacker triggers the leak through specific password-reset request parameters. The primary limiting factor is impact, not access: the flaw only discloses the secret login-URL slug and defeats an obscurity layer - it does not itself bypass authentication, so follow-on value requires valid credentials or a separate login vulnerability. |
| Impact | This is a low-priority, defense-in-depth-defeating information disclosure rather than a direct compromise. The provided CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N = 5.3 MEDIUM) is internally consistent: remotely reachable, no authentication, no user interaction, low-confidentiality-only impact. The single leaked asset is the site's secret login slug - the plugin's entire value proposition is hiding /wp-login.php behind a custom URL, and this bug lets an unauthenticated attacker recover that slug via crafted password-reset request parameters, restoring the very exposure the plugin was installed to prevent. Crucially, this only defeats an obscurity layer: recovering the slug does not grant access; an attacker still needs valid credentials or a separate authentication flaw to actually log in. No EPSS score, no CISA KEV listing, and no public exploit are present in the intelligence provided, so exploitation status is 'no public exploit identified at time of analysis.' The C:L rating is arguably generous given the disclosed data is a URL path rather than user PII or secrets. Real-world risk is modest - it lowers the bar for brute-force/credential-stuffing against the login page but is not independently actionable. |
| Exploit ScenarioDerived | An unauthenticated attacker who knows a target runs Easy Hide Login sends a password-reset request with specific parameters that route them to the standard WordPress login page and echo back the configured secret login slug in the response. Having recovered the hidden slug, the attacker can now reach the login form directly to mount credential-stuffing or brute-force attacks that the plugin was meant to block. No public proof-of-concept is identified in the provided data, though the technique is straightforward given the description. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 23, 2026
The Easy Hide Login WordPress plugin before 1.7 leaves the standard login page reachable when an attacker supplies certain password-reset request parameters, and the resulting page discloses the site's configured secret login slug. Any site running the plugin for its intended purpose (hidden custom login URL) is affected, and exploitation is remote and unauthenticated (CVSS:3.1/AV:N/AC:L/PR:N/UI:N) with no public exploit code identified at time of analysis. Impact is limited to disclosure of the obscurity secret - the flaw does not bypass authentication on its own, so follow-on value requires valid credentials or a separate login flaw, making this a low-priority, defense-in-depth-defeating information disclosure rather than a direct compromise.
RemediationAI
Upgrade the Easy Hide Login WordPress plugin to version 1.7 or later, which is the first release outside the affected '<1.7' range and the fix referenced by the vendor patch availability noted in the source data; verify the installed version from the WordPress Plugins page after updating, since the same vulnerability class was patched only in that release. Patch management is the only complete fix - there is no configuration toggle that closes the password-reset leak while keeping the hidden-login feature working, because the feature itself is what is being bypassed. If immediate upgrade is not possible, compensating controls carry real trade-offs: enabling a WAF rule or server-level block that rejects requests to the default wp-login.php path even when password-reset parameters are appended can close the specific bypass but risks breaking WordPress's legitimate lost-password flow for users, and adding multi-factor authentication or login rate-limiting on the revealed endpoint reduces the follow-on risk of credential stuffing without preventing the slug disclosure itself. Treat any site that ran a version below 1.7 as having had its secret login slug potentially exposed and consider rotating it to a new slug after patching. Consult the vendor advisory at https://wpscan.com/vulnerability/be4e40a1-8f2e-4c80-8615-77cc325c90b6/ for the authoritative fix details.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Easy Hide Login is a WordPress plugin whose entire purpose is to conceal the standard wp-login.php endpoint behind a user-chosen secret slug, so that automated credential-stuffing and brute-force tooling cannot find the authentication form. The plugin implements this by hooking into WordPress's request routing and blocking or redirecting direct access to the default login path. Under the CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) class, the pre-1.7 implementation does not apply that same enforcement to the password-reset code path: when a request is made with particular password-reset parameters, WordPress's lost-password handling renders the login form instead of being intercepted, and the rendered response leaks the configured secret slug. Because the protection is a single shared secret rather than a cryptographic control, once the slug is recovered the attacker knows the exact URL of the real authentication endpoint and can target it directly - the plugin's core defense is effectively negated. CPE/version data from ENISA EUVD lists the affected range as Easy Hide Login 0 through versions less than 1.7, and the disclosure was reported through WPScan.
Know when PHP gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Remote unauthenticated request with no interaction leaks only a secret URL slug (confidentiality-low, no integrity/availability impact); C:L is defensible though arguably generous for an obscurity-only disclosure.
Primary rating from Vendor (wpscan).
CVSS VectorVendor: wpscan
Lifecycle Timeline
4DescriptionCVE.org
The Easy Hide Login WordPress plugin before 1.7 does not fully enforce its hidden-login protection, allowing an unauthenticated attacker to reach the standard login page through certain password-reset request parameters and to recover the site's configured secret login slug from the returned page, defeating the Easy Hide Login WordPress plugin before 1.7's core protection.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
In PHP versions 7.1.x below 7.1.33, 7.2.x below 7.2.24 and 7.3.x below 7.3.11 in certain configurations of FPM setup it
sapi/cgi/cgi_main.c in PHP before 5.3.12 and 5.4.x before 5.4.2, when configured as a CGI script (aka php-cgi), does not
(1) boardData102.php, (2) boardData103.php, (3) boardDataJP.php, (4) boardDataNA.php, and (5) boardDataWW.php in Netgear
The '/common/download_agent_installer.php' script in the Quest KACE System Management Appliance 8.0.318 is accessible by
ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Rated critical severity (C
Roundcube Webmail contains a critical PHP object deserialization vulnerability (CVE-2025-49113, CVSS 9.9) that allows au
Util/PHP/eval-stdin.php in PHPUnit before 4.8.28 and 5.x before 5.6.3 allows remote attackers to execute arbitrary PHP c
Palo Alto Networks PAN-OS management web interface contains an authentication bypass allowing unauthenticated attackers
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
The get_referers function in /opt/ws/bin/sblistpack in Sophos Web Appliance before 3.7.9.1 and 3.8 before 3.8.1.1 allows
The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
EUVD-2026-85037
GHSA-rx89-27rf-3jpj
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB