CVE-2026-32350
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 wpradiant Chocolate House chocolate-house allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Chocolate House: from n/a through <= 1.1.5.
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 confidenceThis is a Missing Authorization vulnerability in the wpradiant Chocolate House WordPress plugin affecting versions up to 1.1.5. The vulnerability allows attackers to exploit incorrectly configured access control security levels, likely enabling unauthorized access to administrative functions or sensitive operations that should require proper authentication and capability verification.
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.
-
Identify Chocolate House plugin installationCheck if the wpradiant Chocolate House plugin is installed in your WordPress environment. Navigate to wp-content/plugins/ or check via WordPress admin Dashboard > Plugins.Affected if The Chocolate House plugin by wpradiant is present in the plugins directory
-
Determine installed plugin versionLocate the main plugin PHP file in wp-content/plugins/chocolate-house/ and read the Version header from the plugin file comment block, or check the version field in WordPress admin > Plugins.Affected if The installed version is 1.1.5 or lower
-
Review plugin for missing capability checksInspect the plugin PHP files for AJAX actions, admin pages, or REST API endpoints that perform sensitive operations. Look for whether current_user_can or similar authorization checks are present before executing privileged operations.Affected if Sensitive plugin functions or admin operations lack proper capability verification (current_user_can checks)
-
Test unauthorized access potentialIf feasible, attempt to access plugin administrative functions from a low-privileged user account or unauthenticated request to verify if authorization is properly enforced.Affected if Low-privileged or unauthenticated users can access admin functions that should require elevated permissions
A user is affected if the Chocolate House plugin is installed with version 1.1.5 or lower and the plugin exposes administrative functions or sensitive operations without verifying user capabilities via current_user_can or equivalent 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 dataUpdate the Chocolate House plugin to the latest version once available and review all plugin functions to ensure proper WordPress capability checks (current_user_can) are implemented before executing privileged operations.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.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-2026-32350 — 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-32350 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