CVE-2024-58136
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedYii 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceYii 2 before 2.0.52 has a vulnerability in its behavior attachment mechanism where behaviors defined with an __class array key are mishandled. This is a regression of CVE-2024-4990 and allows remote attackers to execute arbitrary code via specially crafted behavior attachments. The vulnerability has been actively exploited in the wild between February and April 2025.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.0.52CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Yii 2 framework versionRun 'composer show yiisoft/yii2' or inspect your composer.json/composer.lock file for the yiisoft/yii2 package versionAffected if The version is below 2.0.52 (e.g., 2.0.51, 2.0.50, etc.)
-
Identify behavior configurations using __class keySearch your application codebase for behavior definitions that include a '__class' array key, commonly found in behaviors() methods within controllers or componentsAffected if Any component or controller defines behaviors using the __class array key format
-
Review dynamic behavior attachment logicSearch code for calls to attachBehavior, setBehaviors, or similar methods that accept user-controlled or external inputAffected if Application code dynamically attaches behaviors from untrusted input sources
You are affected if your Yii 2 version is below 2.0.52 and your codebase contains behavior definitions using the __class array key or accepts behavior attachments from untrusted sources.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.0.52
Upgrade Yii 2 to version 2.0.52 or later to patch the vulnerability. Review existing code for any behavior attachments using the __class key pattern as part of the upgrade process.
Yii 2.0.52
- 1. Identify the current Yii 2 version in use by checking the composer.json file for 'yiisoft/yii2' version constraint
- 2. Update the composer.json file to require 'yiisoft/yii2' version '2.0.52' or higher (e.g., '"yiisoft/yii2": "^2.0.52"')
- 3. Run 'composer update yiisoft/yii2' or 'composer update' to install the fixed version
- 4. Run application tests to verify the upgrade does not break existing functionality
- 5. Deploy the updated application to production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-58136 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-58136 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data