# CVE-2026-111278: NivoCart through 2.5.1 CAPTCHA Bypass via Answer Disclosed in Page HTML

> Attackers can bypass CAPTCHA protection in NivoCart by extracting the answer from HTML, enabling automated spam and abuse.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/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:** 15 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-vg5v-fhjm-x73p

## What is CVE-2026-111278?

CVE-2026-111278 is a medium-severity vulnerability in nivocart, published on 15 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NivoCart through 2.5.1 contains a CAPTCHA bypass vulnerability that allows unauthenticated attackers to defeat form protection because the expected code is printed as plain text in the HTML. Attackers can fetch protected forms, extract the captcha_image value with a pattern match, and submit it to automate spam, registrations, reviews, and account deletion requests.

Weakness: CWE-804 (Guessable CAPTCHA)

## Which versions are affected by CVE-2026-111278?


## How do I fix CVE-2026-111278?

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

## Is CVE-2026-111278 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-111278 and fix it if it is affected.

What it is: CVE-2026-111278 is a medium-severity vulnerability in nivocart, published on 15 Oct 2026. 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-2026-111278 in the wild and no public exploit code.

Affected product: nivocart. 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-2026-111278/ (Markdown: https://insights.sbomify.com/CVE-2026-111278/index.md)
```

## Sources

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

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