dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 13 Jul 2023.
FedoraOperating system · Fedoraproject

CVE-2021-44026

CRITICAL · 9.8 CVSS v3.1 Published 2021-11-19
Fix available
A fix is available. Upgrade to 1.3.17 / 1.4.12 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Remotely reachable No privileges Zero-click Patch available

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
Roundcube before 1.3.17 and 1.4.x before 1.4.12 is prone to a potential SQL injection via search or search_params.

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

SQL injection vulnerability in Roundcube's search/search_params functionality affecting versions before 1.3.17 and 1.4.x before 1.4.12, allowing remote unauthenticated attackers to inject malicious SQL queries via the search parameter.

MitigationUpgrade Roundcube to version 1.3.17, 1.4.12, or later 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.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FedoraOperating system
Affected:= 33= 34
Debian LinuxOperating system
Affected:= 9.0= 10.0= 11.0
WebmailApplication
Affected:< 1.3.17>= 1.4.0, < 1.4.12

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Check installed Roundcube version
    Locate the Roundcube version file (typically program/include/iniset.php or check the package manager output: `dpkg -l roundcube` for Debian/Ubuntu or `rpm -qi roundcube` for Fedora/RHEL)
    Affected if Version is below 1.3.17, or between 1.4.0 and 1.4.11 inclusive
  2. Verify search functionality is enabled
    Check the Roundcube configuration file (config/config.inc.php or defaults.inc.php) for the 'search' plugin or feature being loaded, or access the webmail interface and confirm the search box is visible in the mailbox view
    Affected if The search feature is active and accessible to users
  3. Confirm database backend is in use
    Inspect the Roundcube database configuration (config/db.inc.php or config/config.inc.php) to verify a database backend (MySQL, PostgreSQL, SQLite) is configured
    Affected if A SQL database backend is configured as the message store
  4. Test search parameter handling
    As an authenticated user, attempt a search with a single quote in the search field (e.g., search for "'") and observe if SQL error messages appear in the response
    Affected if SQL errors or unexpected database messages are returned in the search results

A user is affected if their Roundcube installation version is below 1.3.17 or falls between 1.4.0 and 1.4.11, the search feature is enabled, and a SQL database backend is in use.

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.

dbcve · scoped
Upgrade available Upgrade to 1.3.17 / 1.4.12 or later
Fixed in 1.3.171.4.12
Vendor patch bugs.debian.org →
Interim mitigation

Upgrade Roundcube to version 1.3.17, 1.4.12, or later to remediate the SQL injection vulnerability.

Recommended fix High confidence

Roundcube 1.3.17 (for 1.3.x users) or 1.4.12 (for 1.4.x users)

  1. For Debian/Fedora systems: Run system package update (e.g., 'apt update && apt upgrade' for Debian, 'dnf update' for Fedora) to receive the patched Roundcube packages
  2. For manual/source installations: Download Roundcube 1.3.17 or 1.4.12 (or later) from the official Roundcube repository (https://roundcube.net/download/)
  3. Extract the new version and replace the existing Roundcube installation files, preserving configuration and user data
  4. Clear any application caches if configured
  5. Verify the upgrade by checking the Roundcube version in the web interface or via command line

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fedora Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get it fixed fast

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

Check whether your project pulls in CVE-2021-44026 — 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-2021-44026 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