dbcve.org
YiiApplication · Yiiframework

CVE-2015-5467

CRITICAL · 9.8 CVSS v3.1 Published 2023-09-21
Fix available
A fix is available. Upgrade to 2.0.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
web\ViewAction in Yii (aka Yii2) 2.x before 2.0.5 allows attackers to execute any local .php file via a relative path in the view parameeter.

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 confidence

The web\ViewAction component in Yii 2.x before 2.0.5 contains a path traversal vulnerability. The view parameter accepts relative paths with traversal sequences (e.g., ../../), allowing unauthenticated attackers to include and execute arbitrary local PHP files on the server, leading to remote code execution.

MitigationUpgrade Yii framework to version 2.0.5 or later which includes proper path sanitization for the view parameter. If immediate upgrading is not feasible, implement input validation to reject paths containing traversal sequences.

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
YiiApplication
Affected:>= 2.0.0, < 2.0.5

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Yii framework version
    Locate the Yii framework version file (typically vendor/yiisoft/yii2/CHANGELOG.md or composer.json) or run `composer show yiisoft/yii2` to see the installed version
    Affected if The installed Yii version is 2.0.0 through 2.0.4 (less than 2.0.5)
  2. Identify controllers using ViewAction
    Search your codebase for usage of \yii\web\ViewAction or 'class' => 'ViewAction' in controller configurations. Check controllers that extend \yii\web\Controller and may handle view rendering
    Affected if Any controller is configured to use ViewAction without additional input validation on the view parameter
  3. Verify view parameter is user-controlled
    Examine the controller code implementing ViewAction to determine if the 'view' parameter comes directly from user input (GET/POST request) without sanitization
    Affected if The view parameter is passed directly from request input without filtering traversal sequences like ../
  4. Test for path traversal exposure
    If ViewAction is in use, attempt a controlled test request with a view parameter containing ../../runtime/logs/app.log or similar path to verify if traversal is possible (only perform on non-production systems)
    Affected if The application allows relative path traversal via the view parameter and returns content from files outside the views directory

You are affected if your Yii 2.x installation is version 2.0.0 through 2.0.4 and your application exposes a ViewAction endpoint where users can control the view parameter without path validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.0.5 or later
Fixed in 2.0.5
Interim mitigation

Upgrade Yii framework to version 2.0.5 or later which includes proper path sanitization for the view parameter. If immediate upgrading is not feasible, implement input validation to reject paths containing traversal sequences.

Recommended fix High confidence

2.0.5

  1. Determine your current Yii 2.x version by checking your composer.json or installed version
  2. Run 'composer require yiisoft/yii2:2.0.5' or update the version constraint in your composer.json to '^2.0.5'
  3. Run 'composer update yiisoft/yii2' to install the fixed version
  4. Test your application thoroughly, particularly any code using web\ViewAction
  5. Deploy the updated version to your production environment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Yii Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-5467 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-5467 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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