CVE-2026-32366
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 · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in robfelty Collapsing Categories collapsing-categories allows Blind SQL Injection.This issue affects Collapsing Categories: from n/a through <= 3.0.9.
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 · high confidenceA blind SQL injection vulnerability exists in the robfelty Collapsing Categories WordPress plugin (versions <= 3.0.9). The vulnerability allows unauthenticated attackers to inject malicious SQL commands through unsanitized input parameters, potentially enabling data exfiltration or database compromise.
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
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L
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 Collapsing Categories plugin is installedAccess WordPress admin panel, go to Plugins > Installed Plugins, and look for 'Collapsing Categories' by robfelty. Alternatively, check the wp-content/plugins/ directory for a folder named 'collapsing-categories' or similar.Affected if The plugin is present in the WordPress installation
-
Determine installed plugin versionIn the WordPress plugins list, click on the plugin to view details, or inspect the main plugin PHP file (usually collapsing-categories.php) and look for the 'Version' header in the plugin comment block. Also check readme.txt for version information.Affected if The version number is 3.0.9 or lower, or if the version cannot be determined but the plugin is present (assume affected)
-
Confirm plugin is activeCheck the WordPress admin plugins page to see if Collapsing Categories has an 'Active' status. The vulnerability is exploitable by unauthenticated users when the plugin is active.Affected if The plugin is active on the WordPress site
-
Identify if plugin handles query parametersReview the plugin code for PHP superglobals ($_GET, $_POST, $_REQUEST) being used in database queries without proper sanitization. Focus on functions that build SQL queries based on category or taxonomy parameters, as SQL injection typically occurs through these vectors.Affected if The plugin processes user-supplied input through query parameters and uses them in database queries without prepared statements or proper escaping
A WordPress site is affected if it has the Collapsing Categories plugin by robfelty installed and active with version 3.0.9 or lower, as the plugin accepts unsanitized input that could be exploited for SQL injection.
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 Collapsing Categories plugin to the latest version once available, or implement proper input validation and parameterized queries to neutralize the SQL injection vectors.
- Consultation2.0 h
- Implementation2.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32366 — 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-32366 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