# CVE-2025-62979: WordPress ACF to REST API plugin <= 3.3.4 - Sensitive Data Exposure vulnerability

> An attacker can retrieve sensitive data embedded in API responses from the ACF to REST API WordPress plugin.

- **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:** 27 Oct 2025
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-75wf-2743-qp5f

## What is CVE-2025-62979?

CVE-2025-62979 is a medium-severity vulnerability in airesvsg ACF to REST API, published on 27 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Insertion of Sensitive Information Into Sent Data vulnerability in airesvsg ACF to REST API acf-to-rest-api allows Retrieve Embedded Sensitive Data.This issue affects ACF to REST API: from n/a through <= 3.3.4.

Weakness: CWE-201 (Insertion of Sensitive Information Into Sent Data)

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


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

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

## Is CVE-2025-62979 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-62979 is a medium-severity vulnerability in airesvsg ACF to REST API, published on 27 Oct 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-62979 in the wild and no public exploit code.

Affected product: airesvsg ACF to REST API. 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-62979/ (Markdown: https://insights.sbomify.com/CVE-2025-62979/index.md)
```

## Sources

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

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