Plugins · collapsing-categories · data as of 2026-11-04
Is Collapsing Categories safe? Known vulnerabilities and latest version
- Latest version
- 3.0.12
- Last updated
- 2026-02-12
- Active installs
- 4,000+
- Known issues on record
- 2
- Unpatched in latest
- 0
- Tested up to WP
- 6.9.11
Adds a widget which uses Javascript to dynamically expand or collapse the set of posts for each category. — by robfelty
What to do
- Update to the latest version (3.0.12). Anything older than 3.0.12 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
- If you cannot update right away, deactivate it until you can.
- Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.
With WP-CLI: wp plugin get collapsing-categories --field=version shows what you run; wp plugin update collapsing-categories updates it.
Check your version
Known vulnerabilities
2 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.
high 8.5 CVE-2026-32366 · published 2026-03-13
SQL injection in Collapsing Categories (3.0.9 and older)
- Affected
- 3.0.9 and older
- Fixed in
- 3.0.12
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Improper 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.
high 7.5 CVE-2024-12025 · published 2024-12-18
SQL injection in Collapsing Categories (3.0.8 and older)
- Affected
- 3.0.8 and older
- Fixed in
- 3.0.9 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The Collapsing Categories plugin for WordPress is vulnerable to SQL Injection via the 'taxonomy' parameter of the /wp-json/collapsing-categories/v1/get REST API in all versions up to, and including, 3.0.8 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
Recent activity
- 2026-02-12 — latest release on wordpress.org (3.0.12).
- 2026-03-13 — SQL injection disclosed (CVE-2026-32366), fixed in 3.0.12.
- 2024-12-18 — SQL injection disclosed (CVE-2024-12025), fixed in 3.0.9.
Get an email when Collapsing Categories has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Collapsing Categories (collapsing-categories) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
- Published this week
- Unpatched in the latest version
- By type of vulnerability
- Plugins by robfelty (2 tracked)
Types found in this plugin: SQL injection (2)
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/collapsing-categories (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/collapsing-categories"><img src="https://laskyr.com/plugins/collapsing-categories/badge.svg" alt="Collapsing Categories vulnerability status"></a>