# CVE-2017-16651: Roundcube Webmail File Disclosure

> Authenticated attackers can read arbitrary files on the server via path traversal in attachment plugins, exposing sensitive configuration data.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 3 Nov 2021 (CISA KEV)
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Nov 2017
- **Updated:** 21 Oct 2025
- **Also known as:** ALPINE-CVE-2017-16651, DEBIAN-CVE-2017-16651, DLA-1193-1, DSA-4030-1, GHSA-6r67-r3jm-88p4, MGASA-2017-0409, UBUNTU-CVE-2017-16651, USN-7200-1

## What is CVE-2017-16651?

CVE-2017-16651 is a high-severity path traversal vulnerability in Debian Debian Linux, published on 9 Nov 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Roundcube Webmail before 1.1.10, 1.2.x before 1.2.7, and 1.3.x before 1.3.3 allows unauthorized access to arbitrary files on the host's filesystem, including configuration files, as exploited in the wild in November 2017. The attacker must be able to authenticate at the target system with a valid username/password as the attack requires an active session. The issue is related to file-based attachment plugins and _task=settings&_action=upload-display&_from=timezone requests.

Weakness: CWE-552 (Files or Directories Accessible to External Parties)

## Which versions are affected by CVE-2017-16651?

It affects 2 products.


Products: Debian Debian Linux, Roundcube Webmail.

## How do I fix CVE-2017-16651?

Upgrade to a fixed version. US federal agencies must fix it by 3 May 2022.

## Is CVE-2017-16651 being exploited?

Yes. Attackers have exploited CVE-2017-16651 in the wild since at least 3 Nov 2021.

Public exploit code:

- Python implementation of Roundcube LFI (CVE-2017-16651) (github_poc): https://github.com/ropbear/CVE-2017-16651
- Roundcube TimeZone Authenticated File Disclosure (metasploit)

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-16651 and fix it if it is affected.

What it is: CVE-2017-16651 is a high-severity path traversal vulnerability in Debian Debian Linux, published on 9 Nov 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2017-16651 in the wild since at least 3 Nov 2021.

Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-16651/ (Markdown: https://insights.sbomify.com/CVE-2017-16651/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-16651
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-16651
- OSV: https://osv.dev/vulnerability/CVE-2017-16651

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-16651/
Summaries are generated and may contain mistakes; the official description above is the record.