# CVE-2026-31858: CraftCMS's `ElementSearchController` Affected by Blind SQL Injection

> Authenticated users can perform blind SQL injection in CraftCMS to extract full database contents via the ElementSearchController.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Mar 2026
- **Updated:** 12 Mar 2026
- **Also known as:** GHSA-g7j6-fmwx-7vp8

## What is CVE-2026-31858?

CVE-2026-31858 is a high-severity SQL injection vulnerability in Craftcms Craft Cms, published on 11 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Craft is a content management system (CMS). The ElementSearchController::actionSearch() endpoint is missing the unset() protection that was added to ElementIndexesController in CVE-2026-25495. 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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-31858?

2 open source packages ship an affected version, including craftcms/cms. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `craftcms/cms` | Packagist | From 5.0.0-RC1 | 5.9.9 |
| `craftcms/cms` | Packagist | From 5.0.0-RC1 | 5.9.9 |

Products: Craftcms Craft Cms.

## How do I fix CVE-2026-31858?

Upgrade craftcms/cms to 5.9.9 or later.

## Is CVE-2026-31858 being exploited?

There is no known exploitation of CVE-2026-31858 in the wild and no public exploit code.

## Other vulnerabilities in Craftcms Craft Cms

- [CVE-2025-32432](https://insights.sbomify.com/CVE-2025-32432/): Craft CMS Code Injection (critical 10.0, exploited in the wild)
- [CVE-2024-56145](https://insights.sbomify.com/CVE-2024-56145/): Craft CMS Code Injection (critical 9.3, exploited in the wild)
- [CVE-2025-23209](https://insights.sbomify.com/CVE-2025-23209/): Craft CMS Code Injection (high 8.1, exploited in the wild)
- [CVE-2025-35939](https://insights.sbomify.com/CVE-2025-35939/): Craft CMS External Control of Assumed-Immutable Web Parameter (medium 6.9, exploited in the wild)
- [CVE-2023-41892](https://insights.sbomify.com/CVE-2023-41892/): Craft CMS Remote Code Execution vulnerability (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-31858 and fix it if it is affected.

What it is: CVE-2026-31858 is a high-severity SQL injection vulnerability in Craftcms Craft Cms, published on 11 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-31858 in the wild and no public exploit code.

Affected packages and fixed versions:
- craftcms/cms (Packagist): affected from 5.0.0-RC1; fixed in 5.9.9
- craftcms/cms (Packagist): affected from 5.0.0-RC1; fixed in 5.9.9

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-31858/ (Markdown: https://insights.sbomify.com/CVE-2026-31858/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-31858
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-31858
- OSV: https://osv.dev/vulnerability/CVE-2026-31858

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-31858/
Summaries are generated and may contain mistakes; the official description above is the record.