Unauthenticated IP restriction bypass via spoofed headers
Published May 17, 2024 · Updated Apr 28, 2026
Authentication bypass in WPMU DEV Defender Security 4.4.1 and earlier allows remote attackers to bypass IP restrictions. The IP-detection path trusts user-supplied forwarding headers as the primary client address, allowing a crafted header to replace the requester's real IP. No account or user interaction is required, but impact depends on an enabled IP restriction and is limited to access that rule would otherwise deny.
Summary
What happened
Authentication bypass in WPMU DEV Defender Security 4.4.1 and earlier allows remote attackers to bypass IP restrictions. The IP-detection path trusts user-supplied forwarding headers as the primary client address, allowing a crafted header to replace the requester's real IP. No account or user interaction is required, but impact depends on an enabled IP restriction and is limited to access that rule would otherwise deny.
The record
- CVE
- CVE-2024-25595
- Published
- May 17, 2024
- Updated
- Apr 28, 2026
- Vendor
- WPMU DEV
- Product
- Defender Security
- Classifications
- CWE-290, CAPEC-554, T1036
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 17, 2024CVE publishedPublication date reported by the CVE source.
- Apr 28, 2026Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=4.4.1
- Affected versionversion=n/a <=4.4.1 changes=[{"at":"4.4.2","status":"unaffected"}]
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
No public exploit references are available in this record.
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