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 by 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 will 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 are very prone 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 situations seen on-line.
Menace monitoring platform The Shadowserver Basis stories that its web scans return 84,925 Roundcube situations susceptible to CVE-2025-49113 as of June 8, 2025.
Most of those situations 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 threat of exploitation and the potential for information theft, the publicity of these situations is a big cybersecurity threat.
System directors are advisable to replace to model 1.6.11 and 1.5.10, which handle CVE-2025-49113, as quickly as potential.
It’s unclear if the flaw is being leveraged in precise assaults and at what scale, however rapid motion is suggested nonetheless.
If upgrading is inconceivable, it is strongly recommended to limit entry to webmail, flip off file uploads, add CSRF safety, block dangerous PHP features, and monitor for exploit indicators.
Patching used to imply advanced scripts, lengthy hours, and limitless fireplace drills. Not anymore.
On this new information, Tines breaks down how fashionable IT orgs are leveling up with automation. Patch sooner, scale back overhead, and give attention to strategic work — no advanced scripts required.