Threats / Yiiframework / CVE-2024-58136
CVE-2024-58136
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Yiiframework Yii vulnerability
Yii Framework contains an improper protection of alternate path vulnerability allowing remote code execution. The flaw affects Yii and downstream products like Craft CMS.
Verdict
Today item — known-exploited.
A remote attacker can exploit path traversal or alternate path handling in Yii to execute arbitrary code without authentication. Active exploitation in the wild indicates immediate risk to deployed instances.
CISA KEV Yes · 2025-05-025EPSS 0.84758 (verify live)6CVSS 93CISA SSVC Exploitation: active · Automatable: no · Impact: total4Exploit Public PoC / detection · nuclei template13
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
9 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-05-02).
Probability (EPSS)
EPSS 0.84758 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H) · Affected: Yiiframework, Yii. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-424 CWE-424.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 22 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a public proof-of-concept / detection template). Catalog entries: nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
WeaknessCWE-424 · CWE-424
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution 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 board1
Front door — unauthenticated access narrative 1
Attacker
I identify that Yii's path protection mechanism fails to properly validate or sanitize alternate file paths, allowing me to access restricted resources or execute code outside intended directories.
Business
Applications built on Yii or dependent frameworks become vulnerable to unauthorized code execution, compromising confidentiality, integrity, and availability of customer data and services.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I craft a request using alternate path syntax or traversal techniques to bypass access controls and reach executable code or sensitive files on the server.
Business
Attackers gain shell access or ability to modify application logic, leading to potential data theft, malware installation, or service disruption affecting business continuity.
3
Lateral reach — past segmentation narrative 3
Attacker
I execute arbitrary commands or deploy malicious payloads through the compromised path handling, establishing persistence or lateral movement within the infrastructure.
Business
Incident response costs, regulatory fines, reputational damage, and mandatory security audits accumulate as the breach scope expands across dependent systems and customer environments.
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