CVE-2020-12641
Published: June 22, 2023
Official Description
Roundcube Webmail contains an remote code execution vulnerability that allows attackers to execute code via shell metacharacters in a configuration setting for im_convert_path or im_identify_path.
CISA KEV Advisory
Roundcube Webmail Remote Code Execution Vulnerability
Roundcube Webmail contains an remote code execution vulnerability that allows attackers to execute code via shell metacharacters in a configuration setting for im_convert_path or im_identify_path.
Apply updates per vendor instructions.
Risk Analysis
This remote code execution vulnerability in Roundcube Webmail allows attackers to execute code by injecting shell metacharacters into specific configuration settings. The high EPSS score of 0.93133 indicates a strong likelihood of exploitation, and its presence in CISA's KEV confirms it is being actively exploited.
This vulnerability is actively exploited in the wild and is part of CISA's Known Exploited Vulnerabilities Catalog. Attackers are leveraging this flaw for remote code execution.
Update Roundcube Webmail to a patched version. Review and sanitize configuration settings, particularly those related to external command paths, to prevent shell metacharacter injection.
Technical Analysis
CVE-2020-12641 requires local access, meaning attackers must already have a foothold on the target system.
Exploitation requires some privileges, which limits the exposure to scenarios where an attacker has already gained initial access.
CISA has added CVE-2020-12641 to the Known Exploited Vulnerabilities (KEV) catalog, confirming active exploitation in the wild. U.S. federal agencies are required to patch this within the mandated timeframe, and all organizations should treat remediation as urgent.
Exploit & PoC Resources
All References (2)
Quick Facts
Recommended Actions
- →Apply vendor patches immediately
- →Monitor CVE-2020-12641 in threat intel feeds
- →Review IDS/IPS signatures for exploitation attempts
- !CISA KEV: Federal agencies must patch per BOD 22-01 timeline
- !Active exploitation confirmed — treat as P1