CVE-2024-58136
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.
do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? Partly. The bug can be reached over the network, so generic WAF rules may stop some attacks. Its weakness type is unknown, so we cannot be more precise.
Also consider: patch
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2024-58136 being exploited?
Yes. CVE-2024-58136 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2024-58136?
CVE-2024-58136 is rated Critical with a CVSS score of 9.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2024-58136?
Yes. A fix has been recorded for CVE-2024-58136. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2024-58136 affect?
CVE-2024-58136 affects yiiframework:yii. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected>= 2 and < 2.0.52
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
public exploits
Detection templates only, no public exploit found: 1 Nuclei template
- Yii2 PHP Framework < 2.0.52 - Remote Code Execution · detection template · critical
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
cisa ssvc
- exploitation
- active
- automatable
- no
- technical impact
- total
Assessed by CISA 2 May 2025 (SSVC 2.0.3).
timeline
- 10 Apr 2025Published
- 2 May 2025Added to CISA KEV (exploited in the wild) · 22 days later
- 2 May 2025CISA SSVC assessment: exploitation active · 1 day later
- 23 May 2025CISA remediation due date (US federal agencies) · 20 days later
- 21 Oct 2025CVE record last updated · 152 days (about 5 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 377 days (about 1 year) later
also known as
- Linkgithub.com /yiisoft/yii2/pull/20232
- Linkgithub.com /yiisoft/yii2/pull/20232#issuecomment-2252459709
- Linkgithub.com /yiisoft/yii2/commit/40fe496eda529fd1d933b56a1022ec32d3cd0b12
- Linkgithub.com /yiisoft/yii2/compare/2.0.51...2.0.52
- Linkyiiframework.com /news/709/please-upgrade-to-yii-2-0-52
- Linksensepost.com /blog/2025/investigating-an-in-the-wild-campaign-using-rce-in-craftcms/
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-58136
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Nuclei templates: detection templates
- OSV: advisory aliases and downstream package versions
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.