Plugins · acf-to-rest-api · data as of 2026-11-04
Is ACF to REST API safe? Known vulnerabilities and latest version
- Status
- Closed 2026-01-02
- Known issues on record
- 3
- Unpatched in latest
- 0
What to do
- Replace it. A closed plugin gets no updates through WordPress, so any hole found from now on stays open.
- Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deleting removes its files; deactivating alone leaves them on the server.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.
With WP-CLI, once you have a replacement: wp plugin deactivate acf-to-rest-api && wp plugin delete acf-to-rest-api
Check your version
Known vulnerabilities
3 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version. 3 record(s) do not state which versions are affected.
medium 4.3 CVE-2025-12030 · published 2026-01-07
Missing authorization check in ACF to REST API (3.3.4 and older)
- Affected
- 3.3.4 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The ACF to REST API plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 3.3.4. This is due to insufficient capability checks in the update_item_permissions_check() method, which only verifies that the current user has the edit_posts capability without checking object-specific permissions (e.g., edit_post($id), edit_user($id), manage_options). This makes it possible for authenticated attackers, with Contributor-level access and above, to modify ACF fields on posts they do not own, any user account, comments, taxonomy terms, and even the global options page via the /wp-json/acf/v3/{type}/{id} endpoints, granted they can authenticate to the site.
medium 5.3 CVE-2025-62979 · published 2025-10-27
Information disclosure in ACF to REST API (3.3.4 and older)
- Affected
- 3.3.4 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
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.
high 7.5 CVE-2020-13700 · published 2020-06-24
Missing authorization check in ACF to REST API (3.1.0 and older)
- Affected
- 3.1.0 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- No login needed
- Range from
- NVD analysis · score by NVD
Details from the advisory
An issue was discovered in the acf-to-rest-api plugin through 3.1.0 for WordPress. It allows an insecure direct object reference via permalinks manipulation, as demonstrated by a wp-json/acf/v3/options/ request that reads sensitive information in the wp_options table, such as the login and pass values.
Recent activity
- 2026-01-02 — closed on wordpress.org (Security Issue).
- 2026-01-07 — Missing authorization check disclosed (CVE-2025-12030), fix version not stated.
- 2025-10-27 — Information disclosure disclosed (CVE-2025-62979), fix version not stated.
- 2020-06-24 — Missing authorization check disclosed (CVE-2020-13700), fix version not stated.
Get an email when ACF to REST API has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for ACF to REST API (acf-to-rest-api) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
Types found in this plugin: Missing authorization (2) · Sensitive data exposure (1)
Where this data comes from
- Version, last update, installs, closure: wordpress.org/plugins/acf-to-rest-api (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/acf-to-rest-api"><img src="https://laskyr.com/plugins/acf-to-rest-api/badge.svg" alt="ACF to REST API vulnerability status"></a>