# CVE-2024-5563: reCAPTCHA bypass in authentication flows

Source: https://junglewise.ai/threats/cve-2024-5563-due-to-an-incomplete-implementation-recaptcha-is-not-applied-to  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-21. Updated: 2026-10-21  
License: CC BY 4.0 with a link back

CVE-2024-5563 · Severity: medium · CVSS 4.8 · Published 2026-10-21

An authentication protection system fails to apply reCAPTCHA validation to certain login pathways, even when the feature is enabled. This allows attackers to conduct brute-force attacks against user accounts without the intended bot-blocking protection, potentially leading to unauthorized account access and data theft.

Technologies: [<UNKNOWN>](https://junglewise.ai/threats/technologies/x-unknown).

## Quick answers

**Is CVE-2024-5563 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2024-5563 being exploited in the wild.

**How severe is CVE-2024-5563?** Medium severity, with a CVSS score of 4.8, published 21 October 2026.

**Which products and versions are affected?** <UNKNOWN>.

**Is there a fix for CVE-2024-5563?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2024-5563 attacked?** It is attacked over the network.

**Am I affected by CVE-2024-5563?** Check whether you run <UNKNOWN>. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

Due to incomplete implementation, reCAPTCHA validation is not enforced in all authentication flows despite the feature being enabled. This allows attackers to bypass brute-force protections and systematically attempt credential combinations without triggering rate-limiting or bot-detection mechanisms. The vulnerability requires network access and no user interaction.

## Affected products

- <UNKNOWN>

## Timeline

- 2026-10-21: disclosed

## References

- [https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-3436/](https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-3436/)

## Related threats

- [System component denial of service vulnerability](https://junglewise.ai/threats/cve-2026-95784-a-vulnerability-exists-in-a-system-component-that-may-under)
- [Hessian remoting authentication bypass with non-root context path](https://junglewise.ai/threats/cve-2026-97874-when-hessian-remoting-is-configured-with-basic-authentication-the)
- [Embedded server weak session ID generation](https://junglewise.ai/threats/cve-2026-111259-the-embedded-server-generates-http-session-identifiers-with-a)
- [Web application request routing security constraint bypass](https://junglewise.ai/threats/cve-2026-111258-the-optional-request-routing-feature-forwards-requests-to-their)
- [SSH administration service authentication bypass](https://junglewise.ai/threats/cve-2026-111239-the-optional-ssh-administration-service-grants-full-access-to)