CVE-2015-7309: The theme editor in Bolt before 2.2.5 does not check the file extension when renaming files, which allows r...

Security readout for executives and security teams

Bolt CMS versions before 2.2.5 let an authenticated user abuse the theme editor to turn a crafted file into executable code by renaming it, then reaching it directly. The attacker needs valid access, but successful abuse can mean server-side code execution, so old Bolt installations deserve attention. Exposure is limited to Bolt CMS installations before 2.2.5 where authenticated users can access the theme editor. Internet-facing admin panels, shared editor accounts, or compromised credentials increase risk. The supplied data does not identify other affected products or versions. Prioritize remediation for any legacy Bolt site still in production, especially if administrative access is reachable from the internet. The issue is old, requires authentication, and is not KEV-listed, but public exploit material and code execution impact make unpatched systems unsuitable for continued exposure. Mitigation focus: Upgrade Bolt CMS to 2.2.5 or later using vendor guidance.; Restrict admin and theme editor access to trusted users only.; Review web server rules to prevent direct execution of uploaded theme files where practical..

Prepared

Jun 13, 2026, 22:03 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.