Skip to main content
Vulnerability Database/CVE-2026-114714

CVE-2026-114714: Roundcube Webmail Path Traversal Flaw

CVE-2026-114714 is a path traversal vulnerability in Roundcube Webmail that allows unauthorized file access through malicious login names. This article covers technical details, affected versions, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-114714 Overview

CVE-2026-114714 is a path traversal vulnerability [CWE-23] in Roundcube Webmail affecting versions before 1.6.20 and 1.7.x before 1.7.5. The flaw resides in the squirrelmail_usercopy plugin, which imports user data from a legacy SquirrelMail installation. When the file-based backend is configured, the plugin builds the source path directly from the login name without stripping path separators. An authenticated user whose login name contains a slash can read and import files from locations outside the configured squirrelmail_data_dir. The Roundcube project patched the issue on October 19, 2026 in releases 1.6.20 and 1.7.5.

Critical Impact

Attackers with a crafted login name can traverse the filesystem and import arbitrary files reachable by the Roundcube process, exposing sensitive data outside the SquirrelMail data directory.

Affected Products

  • Roundcube Webmail versions prior to 1.6.20
  • Roundcube Webmail 1.7.x versions prior to 1.7.5
  • Deployments using the squirrelmail_usercopy plugin with the file-based backend (squirrelmail_driver = 'file')

Discovery Timeline

  • 2026-10-19 - Roundcube releases security updates 1.6.20 and 1.7.5
  • 2026-10-22 - CVE-2026-114714 published to NVD
  • 2026-10-22 - Last updated in NVD database

Technical Details for CVE-2026-114714

Vulnerability Analysis

The squirrelmail_usercopy plugin migrates address books, preferences, and signatures from a legacy SquirrelMail installation into a Roundcube user account during login. With the file-based backend enabled, the plugin derives the source directory from squirrelmail_data_dir and the authenticated user's login name ($uname). The pre-patch code concatenates $uname into the import path without validating that it contains no path separator characters. A login name such as ../../etc/passwd or user/../../private causes the plugin to resolve paths outside the intended data directory and read files accessible to the web server user.

Because the issue requires an authenticated login, exploitation depends on an attacker controlling a login name on the backing authentication system (for example, a provisioning workflow that permits slashes, or an IMAP backend that accepts arbitrary usernames).

Root Cause

The root cause is missing input validation on $uname before it is used in filesystem path construction. The plugin trusted the login name as a safe directory component, violating the principle of path containment required by [CWE-23: Relative Path Traversal].

Attack Vector

Exploitation requires network access to the Roundcube login endpoint and the ability to authenticate with a login name containing a / character. On successful login, the squirrelmail_usercopy plugin reads files from the attacker-controlled path. The import routine then processes those files as if they were SquirrelMail data, allowing disclosure of file contents accessible to the Roundcube process.

php
// Vulnerable code path in plugins/squirrelmail_usercopy/squirrelmail_usercopy.php
// (pre-patch)
if ($rcmail->config->get('squirrelmail_driver') == 'file'
    && ($srcdir = $rcmail->config->get('squirrelmail_data_dir'))) {
    if (($hash_level = $rcmail->config->get('squirrelmail_data_dir_hash_level')) > 0) {
        $srcdir = slashify($srcdir).chunk_split(substr(base_convert(crc32($uname), 10, 16), 0, $hash_level), 1, '/');
    }
    // $uname is appended to $srcdir without checking for '/'
}

Source: Roundcube Commit 15fd175d

Detection Methods for CVE-2026-114714

Indicators of Compromise

  • Authentication events where the submitted username contains a / character or encoded path traversal sequences such as %2F or ...
  • Web server access logs showing successful logins to /index.php?_task=login followed by squirrelmail_usercopy plugin activity for unexpected users.
  • Roundcube error logs referencing failed file reads outside the configured squirrelmail_data_dir.
  • File access by the Roundcube process (for example, www-data) to paths outside the SquirrelMail data directory tree.

Detection Strategies

  • Parse Roundcube and web server logs for login names containing path separators and alert on any match.
  • Correlate authentication telemetry with filesystem auditing (auditd or equivalent) on the Roundcube host to flag reads outside squirrelmail_data_dir.
  • Deploy a WAF or reverse proxy rule rejecting POST bodies to the login endpoint where the _user parameter contains /, \, or URL-encoded equivalents.

Monitoring Recommendations

  • Monitor the installed Roundcube version against 1.6.20 and 1.7.5 across all webmail hosts.
  • Alert on changes to the squirrelmail_usercopy plugin configuration, especially squirrelmail_driver and squirrelmail_data_dir.
  • Track read access to sensitive files (/etc/passwd, SSH keys, mail store files) by the web server user as a secondary signal.

How to Mitigate CVE-2026-114714

Immediate Actions Required

  • Upgrade Roundcube to 1.6.20 or 1.7.5 as published in the Roundcube Security Update Announcement.
  • If upgrading is not immediately feasible, disable the squirrelmail_usercopy plugin in config/config.inc.php by removing it from the plugins array.
  • Audit the backing authentication source to confirm that login names cannot contain / or other path separators.

Patch Information

The fix adds a check that rejects any login name containing a slash before the file-based import path is built. The patches are available in commits 15fd175d and dbdfcac4, and are included in Roundcube Release 1.6.20 and Roundcube Release 1.7.5.

php
// Patched check in plugins/squirrelmail_usercopy/squirrelmail_usercopy.php
if ($rcmail->config->get('squirrelmail_driver') == 'file'
    && ($srcdir = $rcmail->config->get('squirrelmail_data_dir'))
    && strpos($uname, '/') === false // security check
) {
    if (($hash_level = $rcmail->config->get('squirrelmail_data_dir_hash_level')) > 0) {
        $srcdir = slashify($srcdir).chunk_split(substr(base_convert(crc32($uname), 10, 16), 0, $hash_level), 1, '/');
    }
}

Source: Roundcube Commit 15fd175d

Workarounds

  • Disable the squirrelmail_usercopy plugin until the upgrade is applied.
  • Switch the plugin backend away from file if a database backend is available for the SquirrelMail import.
  • Enforce username validation at the reverse proxy or application layer to reject any login containing /, \, or encoded path traversal sequences.
  • Restrict filesystem permissions so the Roundcube process user cannot read files outside the webmail and configured data directories.
bash
# Example: disable the squirrelmail_usercopy plugin in config/config.inc.php
# Before:
# $config['plugins'] = ['archive', 'squirrelmail_usercopy', 'zipdownload'];
# After:
$config['plugins'] = ['archive', 'zipdownload'];

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.