dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-32365

HIGH · 8.5 CVSS v3.1 Published 2026-03-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in robfelty Collapsing Archives collapsing-archives allows Blind SQL Injection.This issue affects Collapsing Archives: from n/a through <= 3.0.7.

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 confidence

The Collapsing Archives WordPress plugin versions 3.0.7 and below contain a blind SQL injection vulnerability due to improper neutralization of special elements in SQL commands. An attacker could inject malicious SQL queries through unsanitized input parameters to extract sensitive data from the database or cause denial of service.

MitigationUpdate the Collapsing Archives plugin to the latest version once available, or implement proper input validation and parameterized queries (prepared statements) for all database interactions to remediate the SQL injection vulnerability.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the Collapsing Archives plugin
    Navigate to WordPress admin > Plugins and find 'Collapsing Archives' in the installed plugins list, or check the wp-content/plugins directory for a folder named 'collapsing-archives'
    Affected if The plugin folder exists in the WordPress installation
  2. Identify the installed version
    Open the plugin's main PHP file (usually collapsing-archives.php) and look for the version comment/header, or check the readme.txt file for the 'Stable tag' or 'Version' entry
    Affected if The version number displayed is 3.0.7 or lower
  3. Confirm the plugin is active
    In WordPress admin > Plugins, verify that Collapsing Archives shows as 'Active' rather than 'Inactive' or 'Not installed'
    Affected if The plugin is currently active on the WordPress site
  4. Check for user input handling in database queries
    Examine the plugin's PHP source code for any $_GET, $_POST, or $_REQUEST parameter usage in SQL queries without prepare() or parameterized statements
    Affected if User-supplied parameters are directly concatenated into SQL queries without sanitization

If the Collapsing Archives plugin is installed with version 3.0.7 or below and is currently active, the environment is affected by this SQL injection vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Collapsing Archives plugin to the latest version once available, or implement proper input validation and parameterized queries (prepared statements) for all database interactions to remediate the SQL injection vulnerability.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32365 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32365 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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