Over 84,000 Roundcube webmail installations are susceptible to CVE-2025-49113, a vital distant code execution (RCE) flaw with a public exploit.
The flaw, which impacts Roundcube variations 1.1.0 via 1.6.10, spanning over a decade, was patched on June 1, 2025, following its discovery and reporting by safety researcher Kirill Firsov.
The bug stems from unsanitized $_GET[‘_from’] enter, enabling PHP object deserialization and session corruption when session keys start with an exclamation mark.
Shortly after the patch was launched, hackers reverse-engineered it to develop a working exploit, which they offered on underground boards.
Although the exploitation of CVE-2025-49113 requires authentication, attackers declare that legitimate credentials might be obtained through CSRF, log scraping, or brute-forced.
Firsov shared technical particulars concerning the flaw on his weblog to assist defend in opposition to energetic exploitation makes an attempt which can be very more likely to happen.
Huge publicity
Roundcube is broadly utilized in shared internet hosting (GoDaddy, Hostinger, OVH) and authorities, training, and tech sectors, with over 1,200,000 cases seen on-line.
Menace monitoring platform The Shadowserver Basis experiences that its web scans return 84,925 Roundcube cases susceptible to CVE-2025-49113 as of June 8, 2025.
Most of those cases are in america (19,500), India (15,500), Germany (13,600), France (3,600), Canada (3,500), and the UK (2,400).

Supply: The Shadowserver Basis
Contemplating the excessive danger of exploitation and the potential for knowledge theft, the publicity of these cases is a major cybersecurity danger.
System directors are beneficial to replace to model 1.6.11 and 1.5.10, which tackle CVE-2025-49113, as quickly as potential.
It’s unclear if the flaw is being leveraged in precise assaults and at what scale, however fast motion is suggested nonetheless.
If upgrading is inconceivable, it is suggested to limit entry to webmail, flip off file uploads, add CSRF safety, block dangerous PHP capabilities, and monitor for exploit indicators.
Patching used to imply complicated scripts, lengthy hours, and infinite fireplace drills. Not anymore.
On this new information, Tines breaks down how trendy IT orgs are leveling up with automation. Patch quicker, cut back overhead, and concentrate on strategic work — no complicated scripts required.