# CVE-2025-42601: Captcha Bypass Vulnerability in Meon KYC solutions

> Remote attackers can bypass Captcha verification in Meon KYC solutions by removing the Captcha parameter from API requests.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Apr 2025
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-gw5v-3q9m-pxcv

## What is CVE-2025-42601?

CVE-2025-42601 is a high-severity vulnerability in Meon KYC solutions, published on 23 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This vulnerability exists in Meon KYC solutions due to insufficient server-side validation of the Captcha in certain API endpoints. A remote attacker could exploit this vulnerability by intercepting the request and removing the Captcha parameter leading to bypassing the Captcha verification mechanism.

Weakness: CWE-602 (Client-Side Enforcement of Server-Side Security)

## Which versions are affected by CVE-2025-42601?


## How do I fix CVE-2025-42601?

No fix has been published for CVE-2025-42601 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-42601 being exploited?

There is no known exploitation of CVE-2025-42601 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-42601 and fix it if it is affected.

What it is: CVE-2025-42601 is a high-severity vulnerability in Meon KYC solutions, published on 23 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-42601 in the wild and no public exploit code.

Affected product: Meon KYC solutions. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-42601/ (Markdown: https://insights.sbomify.com/CVE-2025-42601/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-42601
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-42601
- OSV: https://osv.dev/vulnerability/CVE-2025-42601

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-42601/
Summaries are generated and may contain mistakes; the official description above is the record.