CVE-2023-43770VulnerabilityPublished 22 Sep 2023Updated 21 Oct 2025

CVE-2023-43770: Roundcube Webmail · n/a

Affects Roundcube WebmailSource CVE Database V5

Exploited in the wild · KEV due 4 Mar 2024 · 63% EPSS · fixed in 1.6.3 : patch Roundcube Webmail now.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.1Medium

How severe the flaw is on the 0–10 CVSS scale.

KEV deadline: 4 Mar 2024 US federal agencies must patch by this date; a sensible deadline for everyone else.
EPSS: 63.6% chance of exploitation in 30 days – higher than 99% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.6.3, 1.5.4, 1.4.14

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

Disclosed: evidence found.
CVE published 22 Sep 2023
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: evidence found.
Listed in CISA KEV 143 days after disclosure
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

CVE published
on cve.org
2023-09-22, t = 0
Added to CISA KEV (opens in a new tab)
exploitation confirmed
2024-02-12, 143 days after disclosure
KEV remediation due
US federal deadline
2024-03-04, 164 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade roundcube/roundcubemail to 1.6.3, 1.5.4 or 1.4.14.

Affected software

Product	Affected	Fixed in
GitHubroundcube/roundcubemail`pkg:github/roundcube/roundcubemail`Other threats	Affected <1.4.14 1.5.0 <1.5.4 1.6.0 <1.6.3	Fixed in 1.4.14 1.5.4 1.6.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

Roundcube before 1.4.14, 1.5.x before 1.5.4, and 1.6.x before 1.6.3 allows XSS via text/plain e-mail messages with crafted links because of program/lib/Roundcube/rcube_string_replacer.php behavior.

Impact

For European organizations, this vulnerability poses a moderate risk primarily to confidentiality and integrity of email communications and user sessions. Exploitation could enable attackers to hijack user sessions, steal sensitive email content, or perform actions on behalf of the user within the webmail interface. This could lead to data leakage, unauthorized access to internal communications, and potential lateral movement within networks if email credentials or session tokens are compromised. Organizations relying on Roundcube for email access, especially in sectors like government, education, and SMEs, may face increased risk of targeted phishing campaigns leveraging this vulnerability. The lack of known exploits reduces immediate risk, but the ease of exploitation and widespread deployment of Roundcube necessitate prompt remediation. Additionally, the vulnerability could be leveraged as part of multi-stage attacks to gain footholds in corporate environments. The scope change in the CVSS vector indicates that exploitation can affect resources beyond the vulnerable component, potentially impacting broader systems if session tokens are reused or if webmail integrates with other internal services.

Mitigation

The primary mitigation is to upgrade Roundcube installations to versions 1.4.14, 1.5.4, or 1.6.3 or later, where the vulnerability has been addressed. Organizations should verify their current Roundcube version and apply patches promptly. In parallel, implement strict email content filtering to detect and quarantine suspicious emails containing crafted links or unusual text/plain content. Employ Content Security Policy (CSP) headers on the webmail server to restrict script execution and reduce the impact of XSS attacks. Educate users to be cautious when opening unexpected or suspicious emails, especially those containing links. Consider sandboxing or isolating webmail access environments to limit session token exposure. Monitor webmail logs for unusual activity indicative of exploitation attempts. If upgrading is delayed, disable or restrict the rendering of text/plain emails or links within them as a temporary workaround. Regularly review and update web application firewall (WAF) rules to detect and block XSS payloads targeting Roundcube. Finally, ensure session management uses secure, HttpOnly cookies to reduce the risk of session hijacking.

CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

Timeline

What to do

Affected software

Description

AI analysisMachine-generated, updated 21 Oct 2025, 20:05 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats