CVE-2023-34186
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 Imran Sayed Headless CMS.This issue affects Headless CMS: from n/a through 2.0.3.
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 the Imran Sayed Headless CMS WordPress plugin versions up to 2.0.3 allows unauthenticated or unauthorized users to access certain functionality that should require proper capability checks or authentication.
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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Verify plugin is installedCheck your WordPress installation under wp-content/plugins/ for a folder named 'headless-cms' or similar Imran Sayed plugin directory. Alternatively, go to WordPress Admin > Plugins and look for 'Imran Sayed Headless CMS' or similar naming.Affected if The plugin folder exists in the plugins directory and the plugin is active
-
Check installed versionIn WordPress Admin > Plugins, find the Imran Sayed Headless CMS plugin and note the version number displayed. If using WP-CLI, run: wp plugin list --name='*headless*' or inspect the plugin's main PHP file for the 'Version' header in the plugin comments.Affected if The displayed version is 2.0.3 or lower
-
Identify exposed AJAX handlersExamine the plugin directory for PHP files containing add_action('wp_ajax_...) or add_action('wp_ajax_nopriv_...) calls. Look for handlers that perform sensitive operations (database changes, content creation, settings modifications) without calling current_user_can() or checking nonces.Affected if AJAX endpoints exist that do not verify user capabilities or validate nonces before executing privileged operations
-
Check admin page access controlsReview plugin PHP files for admin menu registrations (add_menu_page, add_submenu_page) and examine the associated page handlers to determine if they include capability checks using current_user_can() before displaying sensitive data or performing actions.Affected if Admin pages lack proper current_user_can() capability checks at the beginning of handler functions
You are affected if the Imran Sayed Headless CMS plugin is installed and active at version 2.0.3 or lower, and unauthenticated or unauthorized users can access functionality that should require proper WordPress capability verification.
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 to version 2.0.4 or later which includes proper authorization checks. If no update is available, review the plugin code for all AJAX handlers and admin pages to add appropriate capability checks using current_user_can() and nonce verification.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-34186 — 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-34186 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