Security readout for executives and security teams
Plain-English summary
This vulnerability can reveal the supposedly hidden WordPress login URL on sites using WPS Hide Login up to version 1.5.4.2. It does not directly compromise the site, but it weakens a control many teams rely on to reduce automated login attacks.
Executive priority
Treat this as a moderate-priority WordPress hardening issue. It is not a direct takeover bug, but it can remove an obscurity layer and increase credential-attack exposure on public sites.
Technical view
CVE-2020-36710 is a network-accessible, unauthenticated login page disclosure issue in WPS Hide Login. CVSS 3.1 is 5.3 with low confidentiality impact and no integrity or availability impact. The source bundle associates it with CWE-863 and vulnerable versions up to and including 1.5.4.2.
Likely exposure
Exposure is limited to WordPress sites running the WPS Hide Login plugin at vulnerable versions and relying on it to obscure the login route. The provided affected metadata is sparse and partly inconsistent, so verify installed plugin version directly.
Exploitation context
The sources do not show CISA KEV listing or confirmed active exploitation. The practical risk is that unauthenticated attackers may discover the login page and then attempt credential brute force attacks.
Researcher notes
The key uncertainty is affected-version metadata: the narrative says versions through 1.5.4.2, while structured affected data is minimal. Validate against Wordfence and vendor/NinTechNet details before making broad exposure claims.
Mitigation direction
- Check vendor guidance for the fixed WPS Hide Login release.
- Upgrade any WPS Hide Login installation at or below 1.5.4.2.
- Do not rely on hidden login URLs as the only login protection.
- Review WordPress login protections against brute force attempts.
Validation and detection
- Inventory WordPress sites using the WPS Hide Login plugin.
- Confirm the installed plugin version on each site.
- Verify whether the hidden login URL remains discoverable after remediation.
- Review authentication logs for unusual login probing or brute force attempts.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2020-36710 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.