# CVE-2025-48243: WordPress reCAPTCHA for all plugin <= 2.26 - Cross Site Request Forgery (CSRF) Vulnerability

> A Cross-Site Request Forgery vulnerability in the reCAPTCHA for all WordPress plugin allows attackers to bypass security controls.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **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:** No
- **Published:** 19 May 2025
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-4f4p-52mc-m3g8

## What is CVE-2025-48243?

CVE-2025-48243 is a medium-severity vulnerability in sminozzi reCAPTCHA for all, published on 19 May 2025. 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

Cross-Site Request Forgery (CSRF) vulnerability in sminozzi reCAPTCHA for all recaptcha-for-all allows Cross Site Request Forgery.This issue affects reCAPTCHA for all: from n/a through <= 2.26.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2025-48243 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-48243 is a medium-severity vulnerability in sminozzi reCAPTCHA for all, published on 19 May 2025. 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 CVE-2025-48243 in the wild and no public exploit code.

Affected product: sminozzi reCAPTCHA for all. 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-48243/ (Markdown: https://insights.sbomify.com/CVE-2025-48243/index.md)
```

## Sources

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

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