WordPress ACF to REST API plugin <= 3.3.4 - Sensitive Data Exposure vulnerability

published 2025-10-27 last yr. modified 2026-10-08 last mo. also EUVD-2025-35966

cvss: 5.3; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 17%
public exploits: 0; none known

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.

Is CVE-2025-62979 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: partial
Assessed: last yr. (2025-10-27)

Exploit prediction

0.26% chance of exploitation in the next 30 days, higher than 17% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.1	5.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected products

airesvsg ACF to REST API

Classification

Weakness

CWE-201 Insertion of Sensitive Information Into Sent Data

Technology feeds

WordPress rss critical rss

References

patchstack.com /database/Wordpress/Plugin/acf-to-rest-api/vulnerability/wordpress-acf-to-rest-api-plugin-3-3-4-sensitive-data
vdb-entry

Sources

CVE List CVE-2025-62979
NVD CVE-2025-62979

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.