CVE-2025-66507

A CAPTCHA bypass vulnerability in the 1Panel authentication API allows an unauthenticated attacker to disable CAPTCHA verification by abusing a client-controlled parameter. Because the server previously trusted this value without proper validation, CAPTCHA protections could be bypassed, enabling automated login attempts and significantly increasing the risk of account takeover (ATO).

Details

The /api/login endpoint accepts a boolean field named ignoreCaptcha directly from the client request body:

"ignoreCaptcha": true

The backend implementation uses this value to determine whether CAPTCHA validation should be performed:

if !req.IgnoreCaptcha {
    if errMsg := captcha.VerifyCode(req.CaptchaID, req.Captcha); errMsg != "" {
        helper.BadAuth(c, errMsg, nil)
        return
    }
}

Because req.IgnoreCaptcha is taken directly from user input, with no server-side validation, no session binding, and no privilege checks, any unauthenticated attacker can force CAPTCHA validation to be skipped.

There are no additional conditions, such as:

no requirement for MFA

no trusted device

no IP reputation checks

no prior valid session

no rate limiting

This results in CAPTCHA being entirely client-controlled, which violates fundamental authentication and anti-automation security assumptions.

CVE-2025-66507 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.0.14, 0.0.0-20251128030527-ac43f00273be); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2025-66507? CVE-2025-66507 is a high-severity security vulnerability in github.com/1Panel-dev/1Panel (go), affecting versions < 2.0.14. It is fixed in 2.0.14, 0.0.0-20251128030527-ac43f00273be.
2. How severe is CVE-2025-66507? CVE-2025-66507 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2025-66507?
   • github.com/1Panel-dev/1Panel (go) (versions < 2.0.14)
   • github.com/1Panel-dev/1Panel/core (go) (versions < 0.0.0-20251128030527-ac43f00273be)
4. Is there a fix for CVE-2025-66507? Yes. CVE-2025-66507 is fixed in 2.0.14, 0.0.0-20251128030527-ac43f00273be. Upgrade to this version or later.
5. Is CVE-2025-66507 exploitable, and should I be worried? Whether CVE-2025-66507 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-66507 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-66507?
   • Upgrade github.com/1Panel-dev/1Panel to 2.0.14 or later
   • Upgrade github.com/1Panel-dev/1Panel/core to 0.0.0-20251128030527-ac43f00273be or later