# CVE-2025-23862: WordPress Contact Form 7 Anti Spambot plugin <= 1.0.1 - Broken Access Control vulnerability

> Attackers can bypass access controls in the Contact Form 7 Anti Spambot plugin due to missing authorization checks.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jan 2025
- **Updated:** 11 May 2026
- **Also known as:** GHSA-mch5-6v3v-jmw3

## What is CVE-2025-23862?

CVE-2025-23862 is a medium-severity missing authorization vulnerability in SzMake Contact Form 7 Anti Spambot, published on 16 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Missing Authorization vulnerability in SzMake Contact Form 7 Anti Spambot contact-form-7-anti-spambot allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Contact Form 7 Anti Spambot: from n/a through <= 1.0.1.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2025-23862 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-23862 is a medium-severity missing authorization vulnerability in SzMake Contact Form 7 Anti Spambot, published on 16 Jan 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-23862 in the wild and no public exploit code.

Affected product: SzMake Contact Form 7 Anti Spambot. 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-23862/ (Markdown: https://insights.sbomify.com/CVE-2025-23862/index.md)
```

## Sources

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

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