dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-8382

MEDIUM · 5.3 CVSS v3.1 Published 2026-05-31
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 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.

NVD · unedited
The Advanced Custom Fields (ACF®) plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 6.8.1. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to overwrite the post_title and post_content of any post bound to a publicly accessible acf_form() instance by injecting values into the _post_title and _post_content parameters of a form submission request.

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.

dbcve analysis · moderate confidence

The ACF plugin fails to verify user authorization when processing form submissions via acf_form(). Unauthenticated attackers can submit values for _post_title and _post_content parameters to modify any post associated with a publicly accessible acf_form() instance, bypassing proper authorization checks.

MitigationUpdate to a patched version of ACF when available, or restrict acf_form() instances to authenticated users only by adding conditional logic (e.g., is_user_logged_in()) around form placements.

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

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.

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

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

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.

dbcve checks

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

  1. Identify installed ACF plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find 'Advanced Custom Fields' version number, or check the plugin file /wp-content/plugins/advanced-custom-fields/acf.php for the 'Version' define
    Affected if version is 6.8.1 or lower (any version up to and including 6.8.1)
  2. Locate acf_form() function calls in theme or plugin files
    Search codebase for 'acf_form(' occurrences in theme files (typically functions.php, page templates) or custom plugin files. Identify which template files or pages render the ACF front-end form
    Affected if acf_form() is present in any publicly accessible template or page
  3. Verify form accessibility settings
    For each found acf_form() call, inspect the function parameters. Look specifically for the 'logged_in' attribute - check if it is set to 'true' or if it is missing entirely. Also check if the form is wrapped in conditional logic that requires authentication
    Affected if the acf_form() call does NOT have 'logged_in' => true set, or the form page is accessible to unauthenticated users without any authorization check
  4. Confirm post binding configuration
    Review the acf_form() settings to identify if a specific post ID is bound via 'post_id' parameter, or if 'new_post' is configured allowing creation of new posts. Check if _post_title or _post_content fields are defined in the ACF field group
    Affected if the form is bound to existing posts (post_id parameter) or creates new posts (new_post parameter) and includes _post_title or _post_content fields

The environment is affected if ACF plugin version is 6.8.1 or lower AND an acf_form() is rendered on a public page without the 'logged_in' attribute set to true, allowing unauthenticated submissions to modify post content.

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version of ACF when available, or restrict acf_form() instances to authenticated users only by adding conditional logic (e.g., is_user_logged_in()) around form placements.

Recommended fix Moderate confidence

ACF 6.8.2 or later

  1. 1. Back up your WordPress database and files before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard.
  3. 3. Locate the Advanced Custom Fields (ACF) plugin in the list.
  4. 4. If an update is available, click 'Update Now' to upgrade to version 6.8.2 or later.
  5. 5. Alternatively, download the latest version from wordpress.org/plugins/advanced-custom-fields/ and upload via Plugins > Add New > Upload Plugin.
  6. 6. After updating, verify the acf_form() instances on your site still function correctly by testing form submissions.
  7. 7. Confirm that unauthenticated users can no longer manipulate _post_title or _post_content parameters to modify posts.
Caveat Minimal risk - patch release focused on security fix; verify custom field form functionality after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8382 — 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 Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

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

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