Second-factor/challenge verification uses PHP loose equality (==) between the submitted response and a $_SESSION value. The session index is only created when a challenge is actually issued, so when no challenge exists it evaluates to NULL, and a request that omits (or empties) the response parameter is also NULL/'' PHP then evaluates NULL == NULL (or '' ==
Explore
Rule Explorer
Search the public rule index by CVE, GHSA, CWE, language, framework, author, or rule slug. Filter by language, framework, severity, confidence, license, and validation status.
- Public rules
- 6965
- Downloads
- 12.9M
- Verified
- 6965
- Authors
- 2
Search the rule indexUse CVE, GHSA, CWE, language, framework, package, or rule slug.
CVE-2026-92914: Php Auth Challenge Loose Equality Bypasscve-2026-92914-php-auth-challenge-loose-equality-bypass
CVE-2026-47841: Spring Webauthn Reference Equality Bypasscve-2026-47841-spring-webauthn-reference-equality-bypass
Comparing WebAuthn types such as UserVerificationRequirement or PublicKeyCredentialType using reference equality (`==` or `!=`) can lead to security bypasses when objects are deserialized from a distributed session store. Use `.equals()` instead.
All matching rules loaded.