# CVE-2022-1801: Very Simple Contact Form < 11.6 - Captcha bypass

> Attackers can bypass captcha protection in the Very Simple Contact Form plugin by reading exposed solutions, facilitating spam submission.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-c8xc-gc49-4vf2

## What is CVE-2022-1801?

CVE-2022-1801 is a high-severity vulnerability in Unknown Very Simple Contact Form, published on 20 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Very Simple Contact Form WordPress plugin before 11.6 exposes the solution to the captcha in the rendered contact form, both as hidden input fields and as plain text in the page, making it very easy for bots to bypass the captcha check, rendering the page a likely target for spam bots.

Weakness: CWE-287 (Improper Authentication), CWE-804 (Guessable CAPTCHA)

## Which versions are affected by CVE-2022-1801?

It affects 1 product.


Products: Very Simple Contact Form Project Very Simple Contact Form.

## How do I fix CVE-2022-1801?

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

## Is CVE-2022-1801 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-1801 and fix it if it is affected.

What it is: CVE-2022-1801 is a high-severity vulnerability in Unknown Very Simple Contact Form, published on 20 Jun 2022. 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-2022-1801 in the wild and no public exploit code.

Affected product: Unknown Very Simple Contact Form. 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-2022-1801/ (Markdown: https://insights.sbomify.com/CVE-2022-1801/index.md)
```

## Sources

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

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