CVE-2023-32094
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 Felix Welberg Extended Post Status allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Extended Post Status: from n/a through 1.0.19.
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 confidenceA missing authorization vulnerability in the Extended Post Status WordPress plugin (versions up to 1.0.19) allows attackers to exploit incorrectly configured access control security levels, potentially enabling unauthorized users to access or manipulate post status functionality that should require higher-level WordPress capabilities.
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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Extended Post Status plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'Extended Post Status' in the list of active plugins.Affected if The Extended Post Status plugin appears in the installed plugins list, regardless of activation status
-
Identify installed plugin versionIn the Plugins list, click on the plugin name or view the plugin details to find the version number displayed (e.g., 'Version 1.0.19' or earlier).Affected if The installed version is 1.0.19 or any earlier version number
-
Review WordPress user roles with access to post status featuresGo to Users > All Users in WordPress admin. Identify which user roles (Administrator, Editor, Author, Contributor, Subscriber) exist and note their capability levels. Cross-reference with the post status functionality the plugin provides.Affected if Users with lower-tier roles (Author, Contributor, Subscriber) exist and the plugin exposes post status controls accessible to them
-
Test for unauthorized access to post status controlsLog in as a non-administrator user (e.g., Author or Contributor). Attempt to access or modify post status settings that should require administrator or editor-level capabilities according to WordPress role definitions.Affected if A lower-privilege user can access, view, or modify post status functionality that should be restricted to higher-capability roles
The environment is affected if the Extended Post Status plugin version 1.0.19 or earlier is installed AND lower-privilege WordPress users can access post status controls that should require higher-level capabilities.
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 Extended Post Status plugin to the latest version beyond 1.0.19 which includes proper authorization checks, or remove the plugin if no longer needed.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-32094 — 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-32094 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