CVE
Craftcms CMS database read via SQL injection in element lookup
Craft CMS 5.0.0 before 5.11.5 is the affected range, and the fix is in 5.11.5. No vendor severity rating is given, so the CVSS score of 7.1 (high) is the only rating listed.
- Exploited
- No known exploitation
- Fix
- Fixed in 5.11.5
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. An authenticated account is required. Public registration enabled, so the attacker can self-register. The target addresses table must contain at least one row for the time-based oracle to fire reliably.
Summary
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.
Who should check
Teams running Craft CMS 5.0.0 up to 5.11.4, especially sites with public registration enabled, where any logged-in user can reach the address actions.
“>= 5.0.0, < 5.11.5”
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
An authenticated account is required. Public registration enabled, so the attacker can self-register. The target addresses table must contain at least one row for the time-based oracle to fire reliably.Upgrade to a fixed version: 5.11.5.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-130673 (Craft CMS 5.0.0 before 5.11.5 SQL Injection via Element::findOne() Criteria), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-130673 (entry last updated 2026-11-18):
Affected:
- craftcms cms: from 5.0.0, fixed in 5.11.5
Fixed versions: 5.11.5.
Conditions (all must be true for the bug to be hit):
- An authenticated account is required. (source: https://github.com/craftcms/cms/security/advisories/GHSA-cphx-cx67-jcqj)
- Public registration enabled, so the attacker can self-register. (source: https://github.com/craftcms/cms/security/advisories/GHSA-cphx-cx67-jcqj)
- The target addresses table must contain at least one row for the time-based oracle to fire reliably. (source: https://github.com/craftcms/cms/security/advisories/GHSA-cphx-cx67-jcqj)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-130673 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130673 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/craftcms/cms/security/advisories/GHSA-cphx-cx67-jcqj
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-130673
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130673"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- craftcms cms
From 5.0.0 · fixed in 5.11.5
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · craftcms/cms · Advisory GHSA-cphx-cx67-jcqj |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130673 |
| Record | NVD · CVE-2026-130673 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130673
Is CVE-2026-130673 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
An SQL injection flaw in the Element::findOne() criteria lets a logged-in account read database contents, including sensitive data, using blind boolean or time-based techniques.Source: github.com
Which versions are affected by CVE-2026-130673?
cms: from 5.0.0 before 5.11.5.Source: cve.now feed data
Am I affected, and how do I check?
Craft CMS versions from 5.0.0 before 5.11.5 are in the affected range. The advisory says an authenticated account is required, and that a site with public registration enabled lets an attacker self-register to get one. The installed version can be checked in the control panel or with composer show craftcms/cms.Source: github.com
How do I fix CVE-2026-130673?
Upgrade Craft CMS to 5.11.5 or later, the fixed version listed for this range.Source: github.com