CVE details
CVE-2026-114722
Roundcube Webmail before 1.6.20 and 1.7.x before 1.7.5 is affected by a CSS scoping bypass in HTML messages. rcube_utils::mod_css_styles() did not treat an at-rule prologue such as @layer a; as a selector boundary, and did not handle selectors beginning with ::, so selectors following an at-rule were left unscoped and applied to the whole Roundcube interface instead of being confined to the message body. This allows an HTML message to restyle application chrome for UI redressing and spoofing. Upstream fixed this in the commit “Fix CSS scoping bypass in HTML messages using at-rules”.
- Score
- 6.5 medium
- Published
- 2026-10-22
- Links
- NVD · cve.org · Report wrong data
Matched ports (15)
| Port | Package | Version | Status | Maintainer |
|---|---|---|---|---|
| mail/roundcube-classic | roundcube-classic-php82 | 1.6.0.4 | unaddressed | brnrd@FreeBSD.org |
| mail/roundcube-classic | roundcube-classic-php83 | 1.6.0.4 | unaddressed | brnrd@FreeBSD.org |
| mail/roundcube-classic | roundcube-classic-php84 | 1.6.0.4 | unaddressed | brnrd@FreeBSD.org |
| mail/roundcube-classic | roundcube-classic-php85 | 1.6.0.4 | unaddressed | brnrd@FreeBSD.org |
| mail/roundcube-classic | roundcube-classic-php86 | 1.6.0.4 | unaddressed | brnrd@FreeBSD.org |
| mail/roundcube-larry | roundcube-larry-php82 | 1.6.1.3 | unaddressed | brnrd@FreeBSD.org |
| mail/roundcube-larry | roundcube-larry-php83 | 1.6.1.3 | unaddressed | brnrd@FreeBSD.org |
| mail/roundcube-larry | roundcube-larry-php84 | 1.6.1.3 | unaddressed | brnrd@FreeBSD.org |
| mail/roundcube-larry | roundcube-larry-php85 | 1.6.1.3 | unaddressed | brnrd@FreeBSD.org |
| mail/roundcube-larry | roundcube-larry-php86 | 1.6.1.3 | unaddressed | brnrd@FreeBSD.org |
| mail/roundcube | roundcube-php82 | 1.7.5,1 | fixed by update | ale@FreeBSD.org |
| mail/roundcube | roundcube-php83 | 1.7.5,1 | fixed by update | ale@FreeBSD.org |
| mail/roundcube | roundcube-php84 | 1.7.5,1 | fixed by update | ale@FreeBSD.org |
| mail/roundcube | roundcube-php85 | 1.7.5,1 | fixed by update | ale@FreeBSD.org |
| mail/roundcube | roundcube-php86 | 1.7.5,1 | fixed by update | ale@FreeBSD.org |
Template for a VuXML entry
Range taken from the CVE record, check it before committing. make newentry in security/vuxml creates the vid.
<vuln vid="FIXME (make newentry)">
<topic>FIXME -- FIXME</topic>
<affects>
<package>
<name>roundcube-classic-php82</name>
<range><lt>1.6.20</lt></range>
</package>
<package>
<name>roundcube-classic-php83</name>
<range><lt>1.6.20</lt></range>
</package>
<package>
<name>roundcube-classic-php84</name>
<range><lt>1.6.20</lt></range>
</package>
<package>
<name>roundcube-classic-php85</name>
<range><lt>1.6.20</lt></range>
</package>
<package>
<name>roundcube-classic-php86</name>
<range><lt>1.6.20</lt></range>
</package>
<package>
<name>roundcube-larry-php82</name>
<range><lt>1.6.20</lt></range>
</package>
<package>
<name>roundcube-larry-php83</name>
<range><lt>1.6.20</lt></range>
</package>
<package>
<name>roundcube-larry-php84</name>
<range><lt>1.6.20</lt></range>
</package>
<package>
<name>roundcube-larry-php85</name>
<range><lt>1.6.20</lt></range>
</package>
<package>
<name>roundcube-larry-php86</name>
<range><lt>1.6.20</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Roundcube Webmail before 1.6.20 and 1.7.x before 1.7.5 is affected by
a CSS scoping bypass in HTML messages. rcube_utils::mod_css_styles()
did not treat an at-rule prologue such as @layer a; as a selector
boundary, and did not handle selectors beginning with ::, so selectors
following an at-rule were left unscoped and applied to the whole
Roundcube interface instead of being confined to the message body.
This allows an HTML message to restyle application chrome for UI
redressing and spoofing. Upstream fixed this in the commit “Fix CSS
scoping bypass in HTML messages using at-rules”.</p>
</body>
</description>
<references>
<cvename>CVE-2026-114722</cvename>
<url>https://nvd.nist.gov/vuln/detail/CVE-2026-114722</url>
</references>
<dates>
<discovery>2026-10-22</discovery>
<entry>2026-10-27</entry>
</dates>
</vuln>