CVE-2018-7269
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 · uneditedThe findByCondition function in framework/db/ActiveRecord.php in Yii 2.x before 2.0.15 allows remote attackers to conduct SQL injection attacks via a findOne() or findAll() call, unless a developer recognizes an undocumented need to sanitize array input.
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 confidenceThe findByCondition function in Yii 2.x ActiveRecord.php before 2.0.15 fails to properly sanitize array keys passed to findOne() and findAll() methods, allowing unauthenticated remote attackers to inject arbitrary SQL commands through unsanitized array input.
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.0, < 2.0.15CVSS 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.0/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.
-
Determine Yii 2.x framework versionLocate the Yii version file (typically vendor/yiisoft/yii2/VERSION or composer.lock) and read the installed version numberAffected if version is 2.0.0 or higher but below 2.0.15
-
Identify ActiveRecord model usageSearch codebase for classes extending yii\db\ActiveRecord that implement findOne() or findAll() methods with array argumentsAffected if ActiveRecord models use findOne() or findAll() with array parameters
-
Trace array input source to findByConditionReview code paths where user-supplied data (GET/POST parameters, JSON input) flows into array keys passed to findOne() or findAll()Affected if unsanitized user input directly populates array keys passed to these finder methods
-
Inspect ActiveRecord.php findByCondition functionExamine vendor/yiisoft/yii2/db/ActiveRecord.php and locate the findByCondition method; verify if array keys are sanitized before SQL constructionAffected if the function does not sanitize array keys and user-controlled arrays can reach this method
You are affected if your Yii 2.x version is below 2.0.15 and your application passes unsanitized user-supplied array keys to findOne() or findAll() methods in ActiveRecord models.
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.15
Upgrade Yii 2.x to version 2.0.15 or later which patches the findByCondition function; alternatively, manually validate and sanitize all array parameters passed to findOne()/findAll() until the upgrade is completed.
Yii 2.0.15 or later
- Check current Yii version in composer.json or run 'composer show yiisoft/yii2'
- Update Yii framework to version 2.0.15 or later: composer require yiisoft/yii2:^2.0.15 or composer update yiisoft/yii2
- Verify the upgrade was successful by checking the installed version
- Run application tests to ensure functionality remains intact after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7269 — 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-2018-7269 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