Security readout for executives and security teams
Plain-English summary
CVE-2024-58136 is a critical Yii 2 framework flaw fixed in Yii 2.0.52. Public sources state it was exploited in the wild from February through April 2025. Organizations running affected Yii 2 code should treat this as urgent because compromise can affect confidentiality, integrity, and availability.
Executive priority
Treat this as a high-priority remediation item. It is critical severity, remotely reachable under the CVSS model, and listed as known exploited. Patch or vendor-confirm affected Yii 2 exposure before routine backlog work.
Technical view
Yii 2 before 2.0.52 mishandles behavior attachment when behavior configuration uses an __class array key. The CVE describes this as a regression of CVE-2024-4990. The CVSS 3.1 score is 9.0 with network attack vector, no required privileges or user interaction, high complexity, changed scope, and high CIA impact.
Likely exposure
Primary exposure is applications or packaged products using Yii 2 before 2.0.52, especially internet-facing PHP applications where attacker-controlled data can reach affected behavior configuration paths. The bundle does not prove every Yii 2 deployment is exploitable.
Exploitation context
Active exploitation is supported by CISA KEV and the CVE description, which says exploitation occurred in the wild during February through April 2025. The SensePost reference describes an in-the-wild campaign involving RCE in CraftCMS, but this response does not infer unsupported product impact beyond the provided sources.
Researcher notes
Evidence is strong for affected Yii 2 before 2.0.52 and for in-the-wild exploitation. Public bundle details do not include a complete exploit chain, exact vulnerable call paths, or all downstream products. Avoid assuming exposure without dependency and route validation.
Mitigation direction
- Upgrade Yii 2 to version 2.0.52 or later.
- Review Yii’s upgrade advisory and release comparison for required application changes.
- Identify products or custom applications that bundle Yii 2.
- Prioritize internet-facing systems and systems handling untrusted requests.
- Monitor vendor advisories for downstream products using Yii 2.
Validation and detection
- Inventory dependency manifests and runtime packages for Yii 2 versions below 2.0.52.
- Confirm production deployments match the remediated dependency version.
- Check exposure of internet-facing PHP applications using Yii 2.
- Review security logs for suspicious activity during and after February 2025.
- Track CISA KEV remediation requirements where applicable.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-424: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2024-58136 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9 (3.1)
- Known Exploited
- Yes
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CISA KEV status
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H2.26Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9CriticalVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/yiisoft/yii2/pull/20232CVE reference
- https://github.com/yiisoft/yii2/commit/40fe496eda529fd1d933b56a1022ec32d3cd0b12CVE reference
- https://github.com/yiisoft/yii2/compare/2.0.51...2.0.52CVE reference
- https://www.yiiframework.com/news/709/please-upgrade-to-yii-2-0-52CVE reference
- https://sensepost.com/blog/2025/investigating-an-in-the-wild-campaign-using-rce-in-craftcms/CVE reference · technical-description
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-58136CVE reference · government-resource
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Protection of Alternate Path
Improper Protection of Alternate Path represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.