---
id: "CVE-2026-114721"
kind: "vulnerability"
aliases: ["CVE-2026-114721"]
title: "Roundcube Webmail: deprecated action aliases bypass disabled_actions setting"
severity: "low"
cvss: 3.1
epss: 0.00296
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["mail", "package", "roundcube", "self-hosted"]
not_affected_if: ["default-config", "fixed-version", "no-disabled-actions"]
published_at: "2026-10-22T02:16:59+00:00"
first_seen_at: "2026-10-23T21:57:30+00:00"
updated_at: "2026-10-25T04:47:25+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-114721", "first_seen_at": "2026-10-23T21:57:30+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-114721", "first_seen_at": "2026-10-24T07:15:52+00:00"}]
---

# Roundcube Webmail: deprecated action aliases bypass disabled_actions setting

Roundcube checked disabled_actions against the action name as requested, so a logged-in user could reach a disabled action by using its deprecated alias. The attacker gets access to a feature the administrator meant to turn off, not code execution.

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

## How to check

- Check the installed Roundcube version in `config/defaults.inc.php` or the package manager; affected if below `1.6.20` on the 1.6 line or below `1.7.5` on the 1.7 line
- Check whether `disabled_actions` is set in `config/config.inc.php`; the bypass only matters if an action is listed there

## Fix

- Upgrade Roundcube Webmail to `1.6.20` or `1.7.5` or later
- Until upgraded, remove reliance on `disabled_actions` for sensitive actions and restrict access at the web server level

## Timeline

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

## From the sources

Roundcube Webmail before 1.6.20 and 1.7.x before 1.7.5 allows the disabled_actions configuration setting to be bypassed. The check compared only the action name as requested, so a remote authenticated attacker could reach an action listed in disabled_actions by requesting it through its deprecated alias instead. Upstream fixed this in the commit “Fix bug where deprecated action aliases bypassed `disabled_actions` setting”, which moves the check into rcmail::action_handler() and resolves aliases before comparing.

---

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