CVE-2025-34086: Bolt CMS vulnerable to authenticated remote code execution

Published Jul 3, 2025
·
Updated

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.

Other sources

Bolt CMS vulnerable to authenticated remote code execution

— Packagist

Affected Software

4 affected components
Bolt CMS<=3.7.0
composer/bolt/bolt<=3.7.0
Boltcms Bolt<=3.7.0
composer/bolt/bolt<=3.7.0

Event History

Jul 3, 2025
CVE Published
via MITRE·07:46 PM
Data Sourced
via MITRE·07:46 PM
DescriptionWeakness
Data Sourced
via OSV·07:46 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:15 PM
DescriptionSeverityWeaknessAffected Software
Advisory Published
via GitHub·09:31 PM
Data Sourced
via GitHub·09:31 PM
DescriptionWeaknessAffected Software
Data Sourced
via Packagist·09:31 PM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2025-34086?

CVE-2025-34086 is considered a critical vulnerability due to its potential for remote code execution.

2

How do I fix CVE-2025-34086?

To remediate CVE-2025-34086, upgrade Bolt CMS to version 3.7.1 or later.

3

Who is affected by CVE-2025-34086?

CVE-2025-34086 affects all users of Bolt CMS versions 3.7.0 and earlier.

4

What types of attacks can exploit CVE-2025-34086?

CVE-2025-34086 can be exploited by authenticated users to inject arbitrary PHP code.

5

Is there a workaround for CVE-2025-34086?

There are no known effective workarounds for CVE-2025-34086, so upgrading is necessary.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203