Security readout for executives and security teams
Plain-English summary
This WordPress ACF issue can let an unauthenticated visitor change a post title or body through a publicly reachable front-end ACF form tied to that post. The main business risk is unauthorized content alteration, such as defacement or misleading page content, not data theft or server takeover based on the provided sources.
Executive priority
Treat this as a near-term content integrity risk for public WordPress properties using ACF front-end forms. Prioritize externally facing sites, marketing pages, and high-trust content where unauthorized edits could harm customers or reputation.
Technical view
ACF through 6.8.1 is described as missing proper authorization checks for front-end acf_form() submissions. Attackers can inject _post_title and _post_content values to overwrite post_title and post_content for posts bound to publicly accessible ACF forms. CVSS is 5.3 with network access, low complexity, no privileges, and low integrity impact.
Likely exposure
Exposure appears limited to WordPress sites using ACF front-end acf_form() instances that are publicly accessible and bound to existing posts. Sites using ACF only in the WordPress admin interface are not shown as exposed by the supplied evidence.
Exploitation context
The bundle marks KEV as false and provides no cited evidence of active exploitation. The vulnerability is unauthenticated and low complexity, but impact is described as limited to post title and content modification.
Researcher notes
Evidence supports CWE-862 authorization bypass tied to form-front.php and a WordPress.org changeset. The affected metadata in the bundle is inconsistent, listing defaultStatus unaffected while the title and description state versions up to 6.8.1. Validate against vendor and Wordfence records before broad conclusions.
Mitigation direction
- Inventory WordPress sites using Advanced Custom Fields through version 6.8.1.
- Identify public front-end acf_form() instances bound to existing posts.
- Restrict or disable affected public forms until vendor guidance is applied.
- Check the vendor advisory or plugin changelog for the fixed ACF release.
- Monitor recent post title and content changes for unauthorized edits.
Validation and detection
- Confirm the installed Advanced Custom Fields version on each WordPress site.
- Search code and templates for public acf_form() usage.
- Verify affected forms require proper authorization before changing existing posts.
- Review web and CMS audit logs around public form submissions.
- Compare recent content revisions for unexpected title or body changes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-8382 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4WordfenceVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- Source timelineWordfence
Disclosed
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/ddb2290d-d4bd-4f70-9fe9-927f49721811?source=cveCVE reference, Wordfence
- https://plugins.trac.wordpress.org/browser/advanced-custom-fields/tags/6.8.0/includes/forms/form-front.php#L243CVE reference, Wordfence
- https://plugins.trac.wordpress.org/changeset/3549586/advanced-custom-fields/trunk/includes/forms/form-front.phpCVE reference, Wordfence
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.