How severe is CVE-2018-7269?

CVE-2018-7269 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2018-7269?

CVE-2018-7269 affects the following packages: yiisoft/yii2-dev (Packagist), yiisoft/yii2-dev (Packagist), yiisoft/yii2-dev (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2018-7269?

Update yiisoft/yii2-dev to 2.0.12.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-7269 is resolved across your whole dependency graph.

How do I detect CVE-2018-7269 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for yiisoft/yii2-dev, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2018-7269 if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is CVE-2018-7269 actively exploited in the wild?

No public exploit code has been indexed for CVE-2018-7269 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2018-7269?

CVE-2018-7269 has an EPSS (Exploit Prediction Scoring System) score of 1.9%, placing it in the 80th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2018-7269?

CVE-2018-7269 is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2018-7269 published, and has it been updated?

CVE-2018-7269 was published on March 21, 2018 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

CRITICAL severity

CVE-2018-7269 — yii2-dev

CRITICAL

CVE-2018-7269 is a critical-severity (CVSS 9.8) SQL Injection vulnerability in yiisoft/yii2-dev. A fix is available for yiisoft/yii2-dev — see the affected versions and patch details below.

Yii SQL injection vulnerability

Also known asGHSA-hhg2-g6h6-c266

Published

Mar 21, 2018

Updated

Oct 24, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs80th percentile — riskier than 80% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected

🐘yiisoft/yii2-dev🐘yiisoft/yii2-dev🐘yiisoft/yii2-dev

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

The 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.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`yiisoft/yii2-dev`	all versions	2.0.12.1`composer require yiisoft/yii2-dev:^2.0.12.1`
🐘Packagist	`yiisoft/yii2-dev`	≥ 2.0.13&&< 2.0.13.2	2.0.13.2`composer require yiisoft/yii2-dev:^2.0.13.2`
🐘Packagist	`yiisoft/yii2-dev`	≥ 2.0.14&&< 2.0.15	2.0.15`composer require yiisoft/yii2-dev:^2.0.15`

Affected Products

1 product · 1 configurations

Application

yiiyiiframework

≥ 2.0.0 && < 2.0.15

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for yiisoft/yii2-dev, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update yiisoft/yii2-dev to 2.0.12.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-7269 is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2018-7269 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

9.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CWE Classification

CWE-89SQL Injection

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

security-advisories

4.8/10

Code-Review10/10

Maintained10/10

Branch-Protection0/10

Assessed Nov 9, 2026

Timeline

Disclosed

Mar 21, 2018

Last updated

Oct 24, 2026

Identifiers

CVE-2018-7269

GHSA-hhg2-g6h6-c266

References

Advisoryyiiframework.com · releasing yii 2 0 15 and database extensions with security fixes Advisorynvd.nist.gov · CVE 2018 7269 Webgithub.com · CVE 2018 7269.yaml Webyiiframework.com · releasing yii 2 0 15 and database extensions with security fixes Packagegithub.com · yii2

Related vulnerabilities

Also affects yiisoft/yii2-dev

This CVE is critical severity — higher than any of the other 6 CVEs affecting yiisoft/yii2-dev (highest there: high).

CVE-2025-2689CVE-2018-8074CVE-2017-11516CVE-2018-6009CVE-2021-3689CVE-2021-3692

Same weakness: CWE-89

This CVE is critical severity — higher than any of the other 2 CVEs with CWE-89 (highest there: moderate).

CVE-2026-88985CVE-2026-62361Browse all CWE-89

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2018-7269 — yii2-dev

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2018-7269 in your dependencies?