# CVE-2026-130673: Craft CMS 5.0.0 before 5.11.5 SQL Injection via Element::findOne() Criteria


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 18 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-cphx-cx67-jcqj, GHSA-hp96-qxfq-853g

## What is CVE-2026-130673?

CVE-2026-130673 is a high-severity vulnerability in craftcms cms, published on 18 Nov 2026. 

### Official description

Craft CMS from 5.0.0 before 5.11.5 contains an sql injection vulnerability that allows authenticated low-privilege users to inject raw SQL by passing nested array parameters into Element::findOne() criteria. Attackers can set the query's where property through endpoints like users/delete-address and users/save-address to perform blind boolean or time-based injection and read database contents.

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

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


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

No fix has been published for CVE-2026-130673 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-130673 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-130673 is a high-severity vulnerability in craftcms cms, published on 18 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-130673 in the wild and no public exploit code.

Affected product: craftcms cms. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-130673/ (Markdown: https://insights.sbomify.com/CVE-2026-130673/index.md)
```

## Sources

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

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