CVE-2025-34086: Bolt CMS · Code Injection
Affects Bolt CMSSource CVE Database V5
Not known to be exploited · public exploit available (Metasploit) · CVSS 7.5 High : upgrade to 3.7.1 as a priority.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 4.2% chance of exploitation in 30 days – higher than 90% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.7.1
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 3 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Upgrade bolt/bolt to 3.7.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| BoltCMS | Affected
| Fixed in– |
GitHubbolt/boltpkg:github/bolt/boltOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users are advised to upgrade to a supported version of Bolt CMS that does not contain this vulnerability. If upgrading is not immediately possible, restrict access to the backend to trusted users only and monitor for suspicious activity.
Description
Bolt CMS versions 3.7.0 and earlier contain a chain of vulnerabilities that together allow an authenticated user to achieve remote code execution. A user with valid credentials can inject arbitrary PHP code into the displayname field of the user profile, which is rendered unsanitized in backend templates. The attacker can then list and rename cached session files via the /async/browse/cache/.sessions and /async/folder/rename endpoints. By renaming a .session file to a path under the publicly accessible /files/ directory with a .php extension, the attacker can turn the injected code into an executable web shell. Finally, the attacker triggers the payload via a crafted HTTP GET request to the rogue file. NOTE: The vendor announced that Bolt 3 reached end-of-life after 31 December 2021.
References
- github.com/bolt/bolt/releases/tag/3.7.1 (opens in a new tab)
- exploit-db.com/exploits/48296 (opens in a new tab)
- rapid7.com/db/modules/exploit/unix/webapp/bolt_authenticated_rce/ (opens in a new tab)
- github.com/bolt/bolt (opens in a new tab)
- boltcms.io/newsitem/major-announcements-bolt-3-eol-bolt-4-2-5-0-releases (opens in a new tab)
- raw.githubusercontent.com/rapid7/metasploit-framework/master/modules/exploits/unix/webapp/bolt_authenticated_rce.rb (opens in a new tab)