Pre-authentication bypass via unescaped LDAP filter username
Published Apr 20, 2026 · Updated Apr 20, 2026
LDAP injection in Roxy-WI 8.2.8.2 and earlier allows remote attackers to bypass authentication through the login username. The check_in_ldap function inserts the raw username into an LDAP filter, uses the first matching entry's DN, and binds that DN with the supplied password. LDAP authentication must be enabled; exploitation generally requires any real LDAP user's password, while no password is required if the directory permits anonymous or unauthenticated binds.
Summary
What happened
LDAP injection in Roxy-WI 8.2.8.2 and earlier allows remote attackers to bypass authentication through the login username. The check_in_ldap function inserts the raw username into an LDAP filter, uses the first matching entry's DN, and binds that DN with the supplied password. LDAP authentication must be enabled; exploitation generally requires any real LDAP user's password, while no password is required if the directory permits anonymous or unauthenticated binds.
The record
- CVE
- CVE-2026-33432
- Published
- Apr 20, 2026
- Updated
- Apr 20, 2026
- Vendor
- Roxy-WI
- Product
- Roxy-WI
- Classifications
- CWE-287, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 20, 2026CVE publishedPublication date reported by the CVE source.
- Apr 20, 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=<= 8.2.8.2
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.
Public exploit references
- GHSA login-request 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