Missing AuthorizationWeakness · CWE-862

CVE-2026-4812

MEDIUM · 5.3 CVSS v3.1 Published 2026-04-15

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

62/100

Remediation priority · Elevated

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

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.

Technical summary

dbcve analysis · moderate confidence

The Advanced Custom Fields (ACF) WordPress plugin versions up to 6.7.0 contain a missing authorization vulnerability in AJAX field query endpoints. These endpoints accept user-supplied filter parameters that can override field-configured access restrictions without proper authorization checks, allowing unauthenticated attackers with access to frontend ACF forms to enumerate and disclose draft/private posts, restricted post types, and other normally restricted data.

MitigationUpdate ACF to version 6.7.1 or later when available. Until then, restrict frontend ACF form access to authenticated users only and implement server-side authorization validation on AJAX endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Check ACF plugin version

Navigate to Plugins > Installed Plugins in the WordPress admin dashboard and locate Advanced Custom Fields. Note the installed version number.

Affected if The installed version is 6.7.0 or earlier (versions up to and including 6.7.0 are affected)
Determine if frontend ACF forms allow unauthenticated access

Review ACF form field group settings and WordPress General > Membership settings to check whether frontend ACF forms can be accessed or submitted by users who are not logged in.

Affected if Frontend ACF forms are accessible to unauthenticated (guest) users
Test AJAX endpoint accessibility without authentication

Send a request to the WordPress AJAX endpoint (wp-admin/admin-ajax.php) with an ACF field query action (such as acf/fields/post_object/query) while logged out, using browser developer tools or a tool like curl to observe the response.

Affected if The AJAX field query endpoints return data to unauthenticated requests

Your environment is affected if ACF version is 6.7.0 or earlier AND either frontend ACF forms or AJAX endpoints are accessible to unauthenticated users, allowing potential enumeration of restricted content.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Update ACF to version 6.7.1 or later when available. Until then, restrict frontend ACF form access to authenticated users only and implement server-side authorization validation on AJAX endpoints.

Have this fixed Scoped from the published advisory

Consultation4.0 h
Implementation8.0 h
Testing6.0 h
Review / QA2.0 h

20.0 hours of engineering $3,500

Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-4812 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4812 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-4812?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here

Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data

At a glance

A fix existsA vendor remedy is published

Severity 5.3 Medium

Exploit likelihood EPSS, next 30 days 0.9%

Remediation

Need this fixed?

Have this fixed 20 hrs · Moderate

Typical engagement from $3,500

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2026-4812 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

Check your environment

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References