basicsecurity.net
Proof, not just disclosure.
Threats / Craft CMS / CVE-2025-35939
CVE-2025-35939 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Craft CMS vulnerability

Craft CMS contains an external control of assumed-immutable web parameter vulnerability allowing unauthenticated attackers to introduce arbitrary values including PHP code to known local file locations.

Verdict

Today item — known-exploited.

An unauthenticated remote attacker can manipulate web parameters to write malicious PHP code to the server filesystem, potentially enabling remote code execution when chained with other vulnerabilities.

CISA KEV Yes · 2025-06-023EPSS 0.01119 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
2 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-06-02).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.01119 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Craft CMS, Craft CMS. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-472 CWE-472.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I craft a malicious HTTP request with arbitrary values targeting a known local file parameter on the Craft CMS application.
Business
The organization's web application becomes a vector for arbitrary code injection without requiring authentication.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I inject PHP code through the vulnerable parameter, writing it to a predictable server-side file location.
Business
Malicious code persists on the server infrastructure, establishing a foothold for further exploitation.
3

Lateral reach — past segmentation narrative 3

Attacker
I chain this vulnerability with CVE-2024-58136 to achieve remote code execution and gain control of the application server.
Business
The organization experiences full compromise of the affected Craft CMS instance and potential lateral movement within the infrastructure.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 2 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by cisa-cg (CNA)
  • Named finder/reporter credit (CVE.org)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • Disclosure & credit2
    Catalogued by cisa-cgCNA
    Credited with finding itJoel Land, undefinedunspecified