Technical impact
VoidAuth before version 1.19.2 contains an access control bypass that allows authenticated users to circumvent stricter ProxyAuth domain rules by including percent‑encoded path separators such as slashes, backslashes, semicolons, or dot segments. When the reverse proxy or backend decodes the request, the encoded characters reconcile with a more permissive rule, giving the user unauthorized access to protected paths.
Affected Systems
The vulnerability affects all VoidAuth releases prior to 1.19.2. The affected product is VoidAuth, managed by voidauth, with any deployment that relies on ProxyAuth for domain restrictions and has not applied the 1.19.2 patch or later. No specific sub‑versions beyond the stated cut‑off are enumerated, so all earlier versions are assumed vulnerable.
Risk and Exploitability
The CVSS score of 7.6 classifies the flaw as high severity. EPSS data is not available, and the vulnerability is not listed in CISA KEV, indicating no known widespread exploitation yet. The likely attack vector requires an authenticated user to send a crafted HTTP request containing encoded separators; thus the threat surface depends on an authenticated session but can still lead to significant confidentiality or integrity loss by exposing restricted resources. Because the flaw can be triggered remotely via normal web traffic, it poses a realistic risk to any exposed VoidAuth instance that permits authenticated ProxyAuth usage.