# CVE-2026-4812: Missing authorization in Advanced Custom Fields (ACF®)

> Unauthenticated attackers can disclose draft, private, or restricted post data via ACF AJAX endpoints due to missing authorization checks.

- **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:** 15 Apr 2026
- **Updated:** 15 Apr 2026
- **Also known as:** GHSA-24rc-w3ff-pw6w

## What is CVE-2026-4812?

CVE-2026-4812 is a medium-severity missing authorization vulnerability in wpengine Advanced Custom Fields (ACF®), published on 15 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Advanced Custom Fields (ACF) plugin for WordPress is vulnerable to Missing Authorization to Arbitrary Post/Page Disclosure in versions up to and including 6.7.0. This is due to AJAX field query endpoints accepting user-supplied filter parameters that override field-configured restrictions without proper authorization checks. This makes it possible for unauthenticated attackers with access to a frontend ACF form to enumerate and disclose information about draft/private posts, restricted post types, and other data that should be restricted by field configuration.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-4812?


## How do I fix CVE-2026-4812?

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

## Is CVE-2026-4812 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-4812 and fix it if it is affected.

What it is: CVE-2026-4812 is a medium-severity missing authorization vulnerability in wpengine Advanced Custom Fields (ACF®), published on 15 Apr 2026. 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-2026-4812 in the wild and no public exploit code.

Affected product: wpengine Advanced Custom Fields (ACF®). 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-2026-4812/ (Markdown: https://insights.sbomify.com/CVE-2026-4812/index.md)
```

## Sources

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

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