p PatchFirst

CVE-2025-34086

CVE-2025-34086 · Bolt CMS Authenticated Remote Code Execution via Profile Injection and File Rename

This page contains facts from public vulnerability sources. Check the original advisory before updating.

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.

CVSS 7.5 · High · EPSS 4.2% · Public exploit

Published
Updated

Stack: php

Affected products and versions

  • cms

    Versions
    • ≥ 0, ≤ 3.7.0: Affected (semver)

    No fix published

  • bolt/bolt Packagist

    Versions
    • 3.5.7
    • v0.8.4
    • v0.8.5
    • v0.9.10
    • v0.9.5
    • v1.0.0
    • v1.0.5
    • v1.1.2
    • v1.1.4
    • v1.2.1
    • v1.3.0
    • v1.4.0
    • v1.4.3
    • v1.5.1
    • v1.5.6
    • v1.6.0
    • v1.6.2
    • v1.6.3
    • v1.6.3.1
    • v1.6.9
    • v2.0.0
    • v2.0.1
    • v2.0.2
    • v2.0.3
    • v2.0.4
    • v2.0.5
    • v2.0.6
    • v2.1.0
    • v2.1.1
    • v2.1.1-pl1
    • v2.1.2
    • v2.1.3
    • v2.1.3-pl1
    • v2.1.4
    • v2.1.4-pl1
    • v2.1.5
    • v2.1.6
    • v2.1.7
    • v2.1.8
    • v2.1.8-pl1
    • v2.1.9
    • v2.2.0
    • v2.2.1
    • v2.2.10
    • v2.2.11
    • v2.2.13
    • v2.2.14
    • v2.2.15
    • v2.2.16
    • v2.2.17
    • v2.2.18
    • v2.2.19
    • v2.2.19-pl1
    • v2.2.2
    • v2.2.20
    • v2.2.21
    • v2.2.22
    • v2.2.23
    • v2.2.24
    • v2.2.25
    • v2.2.3
    • v2.2.4
    • v2.2.5
    • v2.2.6
    • v2.2.7
    • v2.2.8
    • v2.2.9
    • v3.0.0
    • v3.0.1
    • v3.0.10
    • v3.0.11
    • v3.0.12
    • v3.0.2
    • v3.0.3
    • v3.0.4
    • v3.0.5
    • v3.0.6
    • v3.0.7
    • v3.0.8
    • v3.0.9
    • v3.1.0
    • v3.1.1
    • v3.1.2
    • v3.1.3
    • v3.1.4
    • v3.1.5
    • v3.1.6
    • v3.2.0
    • v3.2.1
    • v3.2.10
    • v3.2.11
    • v3.2.12
    • v3.2.13
    • v3.2.14
    • v3.2.15
    • v3.2.16
    • v3.2.17
    • v3.2.18
    • v3.2.19
    • v3.2.2
    • v3.2.20
    • v3.2.3
    • v3.2.4
    • v3.2.5
    • v3.2.6
    • v3.2.7
    • v3.2.8
    • v3.2.9
    • v3.3.0
    • v3.3.1
    • v3.3.2
    • v3.3.3
    • v3.3.4
    • v3.3.5
    • v3.3.6
    • v3.4.0
    • v3.4.1
    • v3.4.10
    • v3.4.11
    • v3.4.2
    • v3.4.3
    • v3.4.4
    • v3.4.5
    • v3.4.6
    • v3.4.7
    • v3.4.8
    • v3.4.9
    • v3.5.0
    • v3.5.1
    • v3.5.2
    • v3.5.3
    • v3.5.4
    • v3.5.5
    • v3.5.6
    • v3.6.0
    • v3.6.0-beta.1
    • v3.6.0-beta.2
    • v3.6.0-beta.3
    • v3.6.0-beta.4
    • v3.6.0-beta.5
    • v3.6.0-beta.6
    • v3.6.0-beta.7
    • v3.6.1
    • v3.6.10
    • v3.6.11
    • v3.6.2
    • v3.6.3
    • v3.6.4
    • v3.6.5
    • v3.6.6
    • v3.6.7
    • v3.6.8
    • v3.6.9
    • v3.7.0
    Affected ranges
    • ECOSYSTEM: ≤ 3.7.0

    No fix published

Original sources

Check your server →