---
id: "CVE-2026-114714"
kind: "vulnerability"
aliases: ["CVE-2026-114714"]
title: "Roundcube: login name path traversal reads files outside data directory"
severity: "medium"
cvss: 5.3
epss: 0.00367
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["package", "php", "roundcube", "self-hosted", "webmail"]
not_affected_if: ["non-file-backend", "patched-version", "plugin-disabled"]
published_at: "2026-10-22T01:16:58+00:00"
first_seen_at: "2026-10-23T21:57:29+00:00"
updated_at: "2026-10-25T04:20:45+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-114714", "first_seen_at": "2026-10-23T21:57:29+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-114714", "first_seen_at": "2026-10-24T07:15:52+00:00"}]
---

# Roundcube: login name path traversal reads files outside data directory

The squirrelmail_usercopy plugin in Roundcube Webmail builds a file path from the login name without rejecting slashes, so a crafted login name can point the import outside the configured data directory. An attacker can make files outside squirrelmail_data_dir be read and imported into the mailbox.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the Roundcube version with `grep -i version program/include/iniset.php` and look at the installed release
- Confirm the squirrelmail_usercopy plugin is enabled in `config/config.inc.php` and that it uses the file based backend with squirrelmail_data_dir set

## Fix

- Upgrade Roundcube Webmail to `1.6.20` or later on the 1.6 line, or to `1.7.5` or later on the 1.7 line
- Until upgraded, disable the squirrelmail_usercopy plugin

## Timeline

- 2026-10-23T21:57:29+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-114714
- 2026-10-24T07:15:52+00:00 epss https://api.first.org/data/v1/epss?cve=CVE-2026-114714

## From the sources

Roundcube Webmail before 1.6.20 and 1.7.x before 1.7.5 is affected by a path traversal vulnerability in the squirrelmail_usercopy plugin. With the file based backend, the source path was built from the login name without rejecting path separators, so a login name containing a slash could cause files outside the configured squirrelmail_data_dir to be read and imported. Upstream fixed this in the commit “Fix unsafe use of a login name in SquirrelMail import file path”, which rejects login names containing a slash.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_