dbcve.org
WebmailApplication · Roundcube

CVE-2026-62644

CRITICAL · 9.8 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 1.6.17 / 1.7.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available 5 weeks old

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
In Roundcube Webmail before 1.6.17 and 1.7.x before 1.7.2, the password plugin of the Roundcube Webmail was subject to username spoofing via session data, which could lead to account takeover.

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 confidence

The password plugin in Roundcube Webmail versions before 1.6.17 and 1.7.x before 1.7.2 contains a username spoofing vulnerability via session data manipulation. An attacker could exploit improper session handling to impersonate legitimate users and change their passwords, achieving full account takeover.

MitigationUpgrade Roundcube Webmail to version 1.6.17, 1.7.2, or later to patch the session data handling vulnerability in the password plugin.

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
WebmailApplication
Affected:>= 1.6.0, < 1.6.17>= 1.7.0, < 1.7.2

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. Identify installed Roundcube Webmail version
    Locate the version file or check the program include directory for the version identifier. Common locations include a VERSION file in the root directory or rcube_version.php in the program/include/ directory. Alternatively, access the Roundcube login page and view the footer for the version number.
    Affected if The installed version falls within >= 1.6.0 and < 1.6.17, or >= 1.7.0 and < 1.7.2.
  2. Verify password plugin is installed
    Check for the presence of the password plugin directory, typically found at plugins/password/ within the Roundcube installation path. Confirm that the password plugin files exist on the system.
    Affected if The password plugin directory exists and is present in the Roundcube installation.
  3. Confirm password plugin is enabled
    Examine the Roundcube main configuration file (usually config/config.inc.php or similar) for the plugins array. Look for an entry referencing the password plugin in the active plugin list.
    Affected if The password plugin is listed in the active plugins configuration and is enabled for use.
  4. Check password plugin configuration
    Inspect the password plugin configuration file (typically plugins/password/config.inc.php) to verify the plugin is actively configured for password change operations. Look for valid driver or password_change settings.
    Affected if The password plugin has an active configuration and is set to handle password modifications.

A user is affected if their Roundcube Webmail version is in the vulnerable range AND the password plugin is installed and enabled, as the flaw requires the password plugin to be active for exploitation.

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.6.17 / 1.7.2 or later
Fixed in 1.6.171.7.2
Vendor patch github.com →
Interim mitigation

Upgrade Roundcube Webmail to version 1.6.17, 1.7.2, or later to patch the session data handling vulnerability in the password plugin.

Recommended fix High confidence

Upgrade to Roundcube Webmail 1.6.17 or 1.7.2 (or later)

  1. 1. Back up your current Roundcube Webmail installation and database
  2. 2. Download Roundcube Webmail version 1.6.17 or 1.7.2 (or later) from the official repository at roundcube.net
  3. 3. Extract the new version to your web server directory
  4. 4. Copy your existing configuration files (config/main.inc.php and config/db.inc.php) to the new installation
  5. 5. Run database schema updates if required: php bin/updatedb.sh
  6. 6. Clear any cached data and session files
  7. 7. Verify the password plugin is functioning correctly
  8. 8. Test that user sessions authenticate correctly without spoofing vulnerability

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

Fix this in Webmail Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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