Skip to content
Server Security Center
KEVcritical9.0

CVE-2024-58136: Yiiframework Yii Improper Protection of Alternate Path

Yiiframework Yii · listed in the CISA catalog of actively exploited vulnerabilities since 2025-05-02.

CVSS v3.1 (CVE record)
9.0
critical
EPSS (exploit probability, 30 days)
88%
higher than 99.7% of all CVEs
Added to CISA KEV
2025-05-02
US federal due date 2025-05-23
Automatable (CISA SSVC)
no
technical impact: total

CVE-2024-58136 explained

CVE-2024-58136 is a flaw in the Yii 2 PHP framework before 2.0.52 that mishandles attaching a behavior defined by an __class array key. It is a regression of CVE-2024-4990. Attackers exploited it in the wild from February through April 2025, and CISA lists it as a known exploited vulnerability.

Impact

A remote attacker needs no privileges and no user interaction to exploit the flaw, although attack complexity is high. Successful exploitation can fully compromise confidentiality, integrity and availability. The scope is changed, so the impact can reach beyond the vulnerable component. CISA rates the technical impact as total, meaning total control of the affected component. It rates the flaw as not automatable, so attacks require manual steps rather than running at scale.

Who is affected

The CVE record lists yiiframework Yii versions ≥ 2, < 2.0.52. That covers Yii 2 from version 2 up to but not including 2.0.52. The fix is in 2.0.52. Applications built on an affected Yii 2 version are exposed until the framework is updated.

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

Official description

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.

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.

  • yiiframework Yii
    Affected
    • ≥ 2, < 2.0.52
    Fixed in
    • 2.0.52

How to fix it

What to do

  1. Update Yii 2 to 2.0.52 or later in every application that uses the framework.
  2. Find all Yii 2 dependencies across your servers and applications, including bundled or vendored copies.
  3. Follow the vendor advisory and apply any mitigations it describes where you cannot update immediately.
  4. Check exposed Yii applications for signs of compromise, since attackers exploited this flaw from February through April 2025.
  5. If no mitigation is possible, follow CISA's required action: apply BOD 22-01 guidance for cloud services or stop using the product.

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

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-424 Improper Protection of Alternate Path

Questions about CVE-2024-58136

Is CVE-2024-58136 being exploited?
Yes. The description says it was exploited in the wild from February through April 2025. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-05-02, with a US federal due date of 2025-05-23. Whether it has been used in ransomware attacks is unknown.
How does it relate to CVE-2024-4990?
CVE-2024-58136 is a regression of CVE-2024-4990. The earlier issue reappeared in how Yii 2 handles behaviors defined by an __class array key. Version 2.0.52 contains the fix.
Which version should we run?
Run Yii 2.0.52 or later. All Yii 2 versions from 2 up to but not including 2.0.52 are affected.

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.