CVE-2026-27046
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 Kaira StoreCustomizer woocustomizer allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects StoreCustomizer: from n/a through <= 2.6.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 Kaira StoreCustomizer woocustomizer WordPress plugin allows authenticated users to access or modify resources beyond their intended permissions due to incorrectly configured access control security levels. The plugin fails to properly verify user capabilities or resource ownership 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
- 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 plugin installationIn WordPress admin, go to Plugins > Installed Plugins and look for 'StoreCustomizer' or 'woocustomizer' by Kaira. Alternatively, check the /wp-content/plugins/ directory for a folder named 'woocustomizer' or similar.Affected if The plugin is not installed on the WordPress site.
-
Identify installed versionIn the WordPress plugin list, find the StoreCustomizer/woocustomizer plugin and note the version number displayed. Or read the main plugin PHP file header for the 'Version' tag.Affected if The installed version falls within the affected version range (compare your version to the known vulnerable versions).
-
Verify user role permissionsCreate or use a test account with a low-privilege role (e.g., Subscriber). Attempt to access the woocustomizer plugin settings page directly via its admin URL, or intercept an AJAX request to plugin endpoints while authenticated as that low-privilege user.Affected if The plugin settings or admin functions are accessible to users without Administrator or Shop Manager capabilities.
-
Inspect AJAX handlers for capability checksExamine the plugin's AJAX action handlers (usually in main PHP files or separate ajax/ folder). Look for function calls that verify user capabilities, such as current_user_can() or wp_verify_nonce() before executing sensitive operations.Affected if The plugin AJAX endpoints lack proper capability checks and allow execution by authenticated users regardless of role.
You are affected if the woocustomizer plugin is installed and allows authenticated users with Subscriber, Contributor, or similar low-privilege roles to access or modify plugin settings and admin 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 dataImplement proper authorization checks (using WordPress capability checks and resource ownership validation) on all sensitive functions and admin pages within the plugin, and ensure all AJAX and form handlers validate user permissions before executing actions.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27046 — 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-27046 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