CVE-2020-35730
XSS in Roundcube Webmail ≤ 1.2.13
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2020-35730 is a medium-severity Cross-site Scripting (CWE-79) vulnerability in Roundcube Webmail. Its CVSS base score is 6.1 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique User Execution (T1204); ranked in the top 2% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
An XSS vulnerability, tracked as CVE-2020-35730 and assigned CWE-79, affects Roundcube Webmail versions prior to 1.2.13, 1.3.x before 1.3.16, and 1.4.x before 1.4.10. The flaw occurs in the linkref_addindex function of rcube_string_replacer.php, which mishandles JavaScript content placed inside link reference elements of incoming plain-text email messages.
An unauthenticated remote attacker can exploit the issue by crafting and sending a plain-text email containing malicious JavaScript within a link reference. When a recipient views the message through the Roundcube web interface, the script executes in the user's browser context, enabling limited cross-origin actions such as reading sensitive data or performing actions on the user's behalf, consistent with the CVSS 6.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N).
The GitHub release tags and commit comparisons for versions 1.2.13, 1.3.16, and 1.4.10 document the patches that correct the improper handling in rcube_string_replacer.php; administrators should upgrade to one of these fixed releases.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2020-23386
Vulnerability Data
An XSS issue was discovered in Roundcube Webmail before 1.2.13, 1.3.x before 1.3.16, and 1.4.x before 1.4.10. The attacker can send a plain text e-mail message, with JavaScript in a link reference element that is mishandled by linkref_addindex in rcube_string_replacer.php.
- CWE(s)
- KEV Date Added
- 22 June 2023
Related Threats
Threat-Actor AttributionAI
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.1.2V1.3.2
Likely Mitigating Controls
Our mappings. Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Penetration testing submits XSS payloads to web applications, detecting cross-site scripting flaws for subsequent remediation.
Validates web inputs to reject script-related content that could produce XSS.
Output validation against expected content can reject or sanitize script content in generated web pages, reducing XSS exploitability.
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
Secure SDLC practices directly target introduction of XSS via coding standards/testing (mostly), yet the single broad outcome leaves many specific neutralization vectors unaddressed (partial).
Patching and EOL replacement can remediate known XSS instances in libraries or frameworks (partial) but do nothing to enforce input neutralization in application code (none).
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
Secure-coding testing and automated code-analysis tools are applied to detect improper neutralization of script-related content during web-page generation.
Training partially blocks XSS exploitation by making users less likely to click on malicious links delivering XSS payloads and by making developers more likely to add some defensive measures, but it does not stop the underlying code defect from being exploitable, consistent with the AT-2 vs CWE-79 blocks=partial calibration anchor.
Secure-coding standards, SAST scans and removal of insecure code samples together eliminate the failure to neutralize script content that produces cross-site scripting flaws.
A.8.8's reach is DISCLOSURE — it sees only instances that carry a vendor-published flaw in third-party components. XSS is overwhelmingly a first-party code defect in custom web applications, which A.8.8's scanning of published advisories and component inventory does not reach; that is A.8.29's territory (SAST/DAST). A.8.8 finds XSS only where it has been published as a CVE in a third-party component (CMS plugins, libraries, etc.), which is a minority of the class.