How severe is GHSA-g7j6-fmwx-7vp8?

No CVSS score has been assigned to GHSA-g7j6-fmwx-7vp8 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-g7j6-fmwx-7vp8?

GHSA-g7j6-fmwx-7vp8 affects the following packages: craftcms/cms (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-g7j6-fmwx-7vp8?

Update craftcms/cms to 5.9.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g7j6-fmwx-7vp8 is resolved across your whole dependency graph.

How do I detect GHSA-g7j6-fmwx-7vp8 in my Packagist dependencies?

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

How do I mitigate GHSA-g7j6-fmwx-7vp8 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 GHSA-g7j6-fmwx-7vp8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-g7j6-fmwx-7vp8 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 GHSA-g7j6-fmwx-7vp8?

GHSA-g7j6-fmwx-7vp8 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 30th 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 GHSA-g7j6-fmwx-7vp8?

GHSA-g7j6-fmwx-7vp8 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 GHSA-g7j6-fmwx-7vp8 published, and has it been updated?

GHSA-g7j6-fmwx-7vp8 was published on March 11, 2026 and was last updated on March 13, 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

CraftCMS's `ElementSearchController` Affected by Blind SQL InjectionGHSA-g7j6-fmwx-7vp8

Fix: craftcms/cms@e1a3dd6

GHSA-g7j6-fmwx-7vp8 is a SQL Injection vulnerability in craftcms/cms. A fix is available for craftcms/cms — see the affected versions and patch details below.

Also known asCVE-2026-31858

Published

Mar 11, 2026

Updated

Mar 13, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-g7j6-fmwx-7vp8.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs30th percentile — riskier than 30% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

🐘craftcms/cms

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 ElementSearchController::actionSearch() endpoint is missing the unset() protection that was added to ElementIndexesController in GHSA-2453-mppf-46cj.

The exact same SQL injection vulnerability (including criteria[orderBy], the original advisory vector) works on this controller because the fix was never applied to it.

Any authenticated control panel user (no admin required) can inject arbitrary SQL via criteria[where], criteria[orderBy], or other query properties, and extract the full database contents via boolean-based blind injection.

Users should update to the patched 5.9.9 release to mitigate the issue.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`craftcms/cms`	≥ 5.0.0-RC1&&< 5.9.9	5.9.9`composer require craftcms/cms:^5.9.9`

Affected Products

1 product · 3 configurations

Application

craft cmscraftcms

≥ 5.0.1 && < 5.9.9

1 version

5.0.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for craftcms/cms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update craftcms/cms to 5.9.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g7j6-fmwx-7vp8 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

The `ElementSearchController::actionSearch()` endpoint is missing the `unset()` protection that was added to ElementIndexesController in [GHSA-2453-mppf-46cj](https://github.com/craftcms/cms/security/advisories/GHSA-2453-mppf-46cj). The exact same SQL injection vulnerability (including `criteria[orderBy]`, the original advisory vector) works on this controller because the fix was never applied to it. Any authenticated control panel user (no admin required) can inject arbitrary SQL via `criteria[where]`, `criteria[orderBy]`, or other query properties, and extract the full database contents vi

O3 Security · Impact-Aware SCA

Is GHSA-g7j6-fmwx-7vp8 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works