Skip to content
CTI Academy Sponsor CTI Academy
CRITICAL · CVSS 9 CISA Known Exploited Vulnerability

CVE-2024-58136

Yiiframework Yii Improper Protection of Alternate Path Vulnerability

Yiiframework Yii

Yii 2 before 2.0.52 mishandles the attaching of behavior that is defined by an __class array key, a CVE-2024-4990 regression, as exploited in the wild in February through April 2025.

CVSS
9
CRITICAL
EPSS
87.8%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
10 Apr 2025
CWE-424

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 2 May 2025. US federal agencies were required to remediate it by 23 May 2025.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 87.8%, which is higher than 99.8% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

Frequently asked questions

Is CVE-2024-58136 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2024-58136.

What does CVE-2024-58136 affect?

CVE-2024-58136 affects Yiiframework Yii. Yii 2 before 2.0.52 mishandles the attaching of behavior that is defined by an __class array key, a CVE-2024-4990 regression, as exploited in the wild in February through April 2025.

How severe is CVE-2024-58136?

CVE-2024-58136 is rated CRITICAL with a CVSS base score of 9. EPSS puts the probability of exploitation in the next 30 days at 87.8%, higher than 99.8% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 23 May 2025.

How should organisations respond to CVE-2024-58136?

Apply the vendor patch for Yiiframework Yii as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.