# GHSA-8mgq-6r2q-82w9: Captcha Bypass in strapi-plugin-ezforms

> Attackers can bypass captcha verification in the ezforms plugin, allowing automated spam submissions without human interaction.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 30 Aug 2022

## What is GHSA-8mgq-6r2q-82w9?

GHSA-8mgq-6r2q-82w9 is a vulnerability in strapi-plugin-ezforms, published on 30 Aug 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

### Impact
Users using any captcha providers

### Patches
>0.1.0

### References
[Issue](https://github.com/excl-networks/strapi-plugin-ezforms/issues/15)

## Which versions are affected by GHSA-8mgq-6r2q-82w9?

2 open source packages ship an affected version, including strapi-plugin-ezforms.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `strapi-plugin-ezforms` | npm | All versions | 0.1.0 |
| `strapi-plugin-ezforms` | npm | All versions | 0.1.0 |

## How do I fix GHSA-8mgq-6r2q-82w9?

Upgrade strapi-plugin-ezforms to 0.1.0 or later.

## Is GHSA-8mgq-6r2q-82w9 being exploited?

There is no known exploitation of GHSA-8mgq-6r2q-82w9 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-8mgq-6r2q-82w9 and fix it if it is affected.

What it is: GHSA-8mgq-6r2q-82w9 is a vulnerability in strapi-plugin-ezforms, published on 30 Aug 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-8mgq-6r2q-82w9 in the wild and no public exploit code.

Affected packages and fixed versions:
- strapi-plugin-ezforms (npm): affected all versions; fixed in 0.1.0
- strapi-plugin-ezforms (npm): affected all versions; fixed in 0.1.0

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/GHSA-8mgq-6r2q-82w9/ (Markdown: https://insights.sbomify.com/GHSA-8mgq-6r2q-82w9/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-8mgq-6r2q-82w9

---
From sbomify Insights: https://insights.sbomify.com/GHSA-8mgq-6r2q-82w9/
Summaries are generated and may contain mistakes; the official description above is the record.