CVE-2026-22348
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 Tasos Fel Civic Cookie Control civic-cookie-control-8 allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Civic Cookie Control: from n/a through <= 1.53.
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 confidenceThe Civic Cookie Control plugin versions through 1.53 contains a missing authorization vulnerability that allows attackers to exploit incorrectly configured access control security levels. This likely enables unauthenticated or unauthorized users to access functionality or data that should be restricted, due to improper or missing capability checks before performing sensitive operations.
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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.
-
Verify Civic Cookie Control plugin installation and versionIn WordPress admin, go to Plugins > Installed Plugins and look for 'Civic Cookie Control' or 'Cookie Control'. Check the version number displayed. Alternatively, inspect the plugin main file header in wp-content/plugins/cookie-control/ or similar path.Affected if The plugin is installed and the version is 1.53 or any earlier version (1.0 through 1.53).
-
Confirm WordPress user registration is enabledIn WordPress admin, go to Settings > General and check 'Anyone can register' setting, or inspect the site's wp-options database table for 'users_can_register' value set to 1.Affected if User registration is enabled on the site, allowing potential unauthorized users to register and potentially exploit missing capability checks.
-
Inspect plugin admin capability requirementsExamine the main plugin PHP file for add_menu_page, add_submenu_page, or admin_menu hook calls and check the 'capability' or 'manage_options' parameter passed to them. Look for any hooks handling AJAX actions or public-facing endpoints.Affected if The plugin uses a weak capability (like 'edit_posts' or no capability check) or has AJAX/public endpoints without current_user_can() verification.
-
Review WordPress user roles and capabilitiesUse a role manager plugin or query wp_options for 'wp_user_roles' to examine defined roles. Check if default roles have elevated capabilities that should be restricted.Affected if Non-admin users have capabilities beyond what is intended, or the site uses roles with elevated permissions that could be exploited.
The environment is affected if the Civic Cookie Control plugin versions 1.0 through 1.53 is installed on WordPress with user registration enabled or with insufficient capability checks on plugin functions.
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 a patched version of the Civic Cookie Control plugin when available. Until then, implement additional access controls at the server level (e.g., restrict admin-area access by IP, ensure strong authentication) and review user role capabilities.
- Consultation3.0 h
- Implementation6.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22348 — 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-2026-22348 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