# CVE-2023-41862: WordPress VS Contact Form plugin <= 14.0 - Sum Captcha Bypass vulnerability

> Attackers can bypass the Sum Captcha security feature in the VS Contact Form plugin, allowing unauthorized form submissions.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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:** 13 Dec 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-69r7-7qx9-rhm7

## What is CVE-2023-41862?

CVE-2023-41862 is a medium-severity vulnerability in Guido VS Contact Form, published on 13 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Weak Authentication vulnerability in Guido VS Contact Form allows Authentication Abuse.This issue affects VS Contact Form: from n/a through 14.0.

Weakness: CWE-1390 (Weak Authentication)

## Which versions are affected by CVE-2023-41862?


## How do I fix CVE-2023-41862?

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

## Is CVE-2023-41862 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-41862 and fix it if it is affected.

What it is: CVE-2023-41862 is a medium-severity vulnerability in Guido VS Contact Form, published on 13 Dec 2024. 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-2023-41862 in the wild and no public exploit code.

Affected product: Guido VS 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-2023-41862/ (Markdown: https://insights.sbomify.com/CVE-2023-41862/index.md)
```

## Sources

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

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