Login-page disclosure via unchecked post_password branch
Published Mar 1, 2021 · Updated Aug 3, 2024
Authentication bypass in WPS Hide Login 1.6.1 allows remote attackers to expose the standard WordPress login page via a crafted POST. In classes/plugin.php, wp_loaded() checks only for the absence of post_password and has no alternate branch, so supplying the field skips request interception. No authentication is required; the bypass reveals the otherwise hidden login endpoint but does not itself grant account access.
Summary
What happened
Authentication bypass in WPS Hide Login 1.6.1 allows remote attackers to expose the standard WordPress login page via a crafted POST. In classes/plugin.php, wp_loaded() checks only for the absence of post_password and has no alternate branch, so supplying the field skips request interception. No authentication is required; the bypass reveals the otherwise hidden login endpoint but does not itself grant account access.
The record
- CVE
- CVE-2021-3332
- Published
- Mar 1, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-287
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 1, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Crafted post_password POST proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo