CVE-2023-22676
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 · uneditedMissing Authorization vulnerability in Anders Thorborg.This issue affects Anders Thorborg: from n/a through 1.4.12.
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 confidenceMissing Authorization vulnerability in Anders Thorborg (versions through 1.4.12). The application fails to properly enforce authorization checks, allowing authenticated or unauthenticated users to access functionality they should not have permission to use. The high CVSS score of 8.8 indicates significant risk with network-exploitable attack vector and high confidentiality/integrity impact.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.4.12CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 plugin installation and activation statusNavigate to WordPress Admin > Plugins and verify whether 'Andersthorborg Advanced Custom Fields' or similar named plugin by Anders Thorborg is installed and activeAffected if The plugin is installed and active in the WordPress environment
-
Identify installed plugin versionIn WordPress Admin > Plugins, locate the plugin and view the version number displayed, or inspect the plugin main file header in wp-content/plugins/ for the 'Version' tagAffected if The installed version is 1.4.12 or any earlier version (1.4.12 and below)
-
Check for exposed administrative endpointsReview the plugin directory for PHP files containing AJAX action handlers (wp_ajax_), admin menu registrations, or form processing logic. Test common WordPress admin-ajax.php endpoints using the plugin's registered actions with low-privilege or unauthenticated requestsAffected if Administrative actions or sensitive functions are accessible without proper capability or authorization checks
-
Audit user role and capability enforcementUsing a role management tool or by inspecting plugin code, verify whether the plugin enforces proper user capabilities (such as 'manage_options', 'edit_posts', or custom capabilities) before executing privileged operationsAffected if The plugin allows unauthenticated users or users lacking required capabilities to execute privileged operations
Your environment is affected if the Anders Thorborg Advanced Custom Fields plugin (version 1.4.12 or lower) is installed and active, and sensitive functionality can be accessed without proper authorization checks.
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 dataImplement proper authorization checks on all sensitive endpoints and functions. Verify user permissions before executing any privileged operations, and enforce role-based or attribute-based access control consistently across the application.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2023-22676 — 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-22676 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