Skip to content
Server Security Center
KEVmedium5.3

CVE-2025-35939: Craft CMS External Control of Assumed-Immutable Web Parameter

Craft CMS · listed in the CISA catalog of actively exploited vulnerabilities since 2025-06-02.

CVSS v3.1 (CVE record)
5.3
medium
EPSS (exploit probability, 30 days)
1.4%
higher than 72.6% of all CVEs
Added to CISA KEV
2025-06-02
US federal due date 2025-06-23
Automatable (CISA SSVC)
yes
technical impact: partial

CVE-2025-35939 explained

CVE-2025-35939 is a flaw in Craft CMS in which content supplied by unauthenticated users is stored, unsanitized, in server-side PHP session files at a known location. The stored content, such as PHP code, could be accessed and executed, possibly by chaining an independent vulnerability. CISA lists it as known to be exploited.

Impact

An unauthenticated remote attacker can write arbitrary values, including PHP code, into a session file at a known local path on the server. No user interaction is needed. On its own the direct impact is limited to integrity. CISA rates it automatable with partial technical impact. Combined with another vulnerability that can access or execute that file, it could lead to code execution.

Who is affected

The CVE record lists Craft CMS versions below 4.15.3 and below 5.7.5 as affected. The fix is in 4.15.3 and 5.7.5. Administrators should move to whichever of these fixed releases matches the release line they currently run.

Written with AI from the data on this page and checked against it automatically.

Official description

Craft CMS stores arbitrary content provided by unauthenticated users in session files. This content could be accessed and executed, possibly using an independent vulnerability. Craft CMS redirects requests that require authentication to the login page and generates a session file on the server at '/var/lib/php/sessions'.

Such session files are named 'sess_[session_value]', where '[session_value]' is provided to the client in a 'Set-Cookie' response header. Craft CMS stores the return URL requested by the client without sanitizing parameters. Consequently, an unauthenticated client can introduce arbitrary values, such as PHP code, to a known local file location on the server.

Craft CMS versions 5.7.5 and 4.15.3 have been released to address this issue.

CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Craft CMS
    Affected
    • < 4.15.3
    • < 5.7.5
    Fixed in
    • 4.15.3
    • 5.7.5

How to fix it

  • Update to a fixed version: 4.15.3, 5.7.5.
  • Vendor advisory: github.com/craftcms/cms/pull/17220
  • CISA's deadline for US federal agencies: 2025-06-23 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Update Craft CMS to 4.15.3 or 5.7.5, matching your current release line.
  2. Follow the vendor advisory and apply any mitigations it describes.
  3. Review PHP session files in '/var/lib/php/sessions' for unexpected content such as PHP code.
  4. Check servers for signs of compromise, especially other vulnerabilities that could execute local files.
  5. Meet CISA's required action: apply mitigations per vendor instructions or discontinue use if mitigations are unavailable.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
Yes – attackers can automate it at scale
Technical impact
Partial – limited control or information

Weakness: CWE-472 External Control of Assumed-Immutable Web Parameter

Questions about CVE-2025-35939

Is this vulnerability being exploited?
Yes. CISA added CVE-2025-35939 to its Known Exploited Vulnerabilities catalog on 2025-06-02, with a US federal due date of 2025-06-23. Whether it is used in ransomware campaigns is unknown.
Does an attacker need an account?
No. An unauthenticated client can place arbitrary content in a session file because Craft CMS stores the requested return URL without sanitizing its parameters.
Why is the score medium if it is exploited?
On its own the flaw only writes content to a session file. Executing that content may require an independent vulnerability, which is why the direct impact is rated low integrity.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.