CVE-2023-7286
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 · uneditedThe plugin ACF Quick Edit Fields for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 3.2.2. This makes it possible for attackers without the edit_users capability to access metadata of other users, this includes contributor-level users and above.
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 · high confidenceThe ACF Quick Edit Fields WordPress plugin (versions up to 3.2.2) contains an Insecure Direct Object Reference vulnerability that allows contributor-level and higher privileged users to access metadata belonging to other users, due to missing authorization checks on the metadata retrieval function.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm ACF Quick Edit Fields plugin is installedLog in to WordPress admin dashboard, navigate to Plugins > Installed Plugins, and look for 'ACF Quick Edit Fields' in the list of active pluginsAffected if The plugin is not installed or not active - if not present, they are not affected by this specific vulnerability
-
Identify installed plugin versionIn the Plugins list, click on 'View Details' next to ACF Quick Edit Fields or check the plugin header in the main plugin file (wp-content/plugins/acf-quick-edit-fields/) to find the version numberAffected if Version is 3.2.2 or any earlier version up to and including 3.2.2 - versions 3.2.2 and below are vulnerable
-
Verify metadata retrieval functionality is accessibleReview the plugin settings under ACF > Quick Edit to confirm metadata fields are configured and the quick edit feature is enabled for user metadata or post metadataAffected if The plugin has active metadata field configurations - if no metadata fields are set up, the attack surface is reduced but the vulnerability still exists in the code
-
Audit user role assignmentsNavigate to Users > All Users in WordPress admin and review which users have Contributor, Author, Editor, or Administrator roles, as these roles can exploit the IDOR flawAffected if There are users with Contributor-level or higher privileges - the vulnerability specifically allows these users to access metadata belonging to other users
A user is affected if ACF Quick Edit Fields plugin versions 3.2.2 or below are installed AND users with Contributor-level or higher privileges exist on the site, regardless of whether metadata fields are actively configured
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate the ACF Quick Edit Fields plugin to version 3.2.3 or later to patch the IDOR vulnerability. If immediate update is not possible, review user role assignments and limit contributor-level access until the patch can be applied.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-7286 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-7286 in production — separate from our analysis above.
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.
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.
- 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