basicsecurity.net
Proof, not just disclosure.
Threats / Roundcube / CVE-2021-44026
CVE-2021-44026 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Roundcube Webmail vulnerability

Roundcube Webmail contains a SQL injection vulnerability in search functionality that allows attackers to execute arbitrary database queries.

Verdict

Today item — known-exploited.

SQL injection via search parameters in Roundcube Webmail enables unauthenticated or authenticated attackers to manipulate database queries, potentially leading to unauthorized data access, modification, or deletion of email and user information.

CISA KEV Yes · 2023-06-223EPSS 0.42908 (verify live)4Exploit Weaponized · public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
10 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2023-06-22).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.42908 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Roundcube, Roundcube Webmail. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-89 SQL Injection — weakness family: Injection.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-89 · SQL InjectionInjection
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I craft malicious SQL syntax in search or search_params fields to break out of the intended query context.
Business
Attacker gains unauthorized access to sensitive email data, user credentials, and personal information stored in the Roundcube database.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I execute database queries to enumerate schema, extract user accounts, and retrieve authentication tokens or session data.
Business
Compromise of user accounts enables lateral movement, credential theft, and impersonation of legitimate webmail users.
3

Lateral reach — past segmentation narrative 3

Attacker
I modify or delete database records to alter email contents, user settings, or administrative configurations.
Business
Loss of data integrity, disruption of email services, and potential regulatory violations related to data protection and audit trails.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • Weaponized exploit available (VulnCheck)
  • 10 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by mitre (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by mitreCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.