On this page (7 sections)
A critical SQL injection flaw, tracked as CVE-2026-123488, affects Craft CMS in the 4.x and 5.x lines. According to the GitHub Advisory Database entry, it sits in the element search endpoint and can be reached without logging in.
If you run Craft CMS, or manage sites for clients who do, check your version today. The advisory describes a path from a remote request to administrator access. Public coverage is thin so far, so treat the details below as what the advisory says, not as a full independent analysis.
What happened
The NVD record was published on November 6, 2026, the same day the advisory appeared in the GitHub Advisory Database. Both carry identical wording, so they should be read as one source, not two confirmations. A VulnCheck advisory and a Craft CMS project advisory (GHSA-qcvp-ggx3-97r6) are also referenced, but their contents were not available in the research, so this article does not rely on them for details.
Technical details in plain terms
SQL injection happens when an application builds a database query by gluing user-supplied text into it, instead of passing that text as a separate, safely handled value. If the input is not cleaned, an attacker can change what the query does.
Per the advisory, the element search endpoint takes an attribute parameter and concatenates it into the query without sanitizing it. It also says that emulated PDO prepares allow stacked statements. In simple terms, that setting lets a single database call carry more than one statement, which widens what an injected value can do from reading data to changing it.
The advisory states the impact: remote attackers can read and write the database, for example by setting the admin flag or overwriting password hashes in the users table to gain administrator access. The CVSS v4 metrics list network attack vector, low complexity, no privileges and no user interaction, with high confidentiality, integrity and availability impact on the vulnerable system.
Who is affected
- Craft CMS 4.x sites running any version from 4.0.0 up to, but not including, 4.18.9.
- Craft CMS 5.x sites running any version from 5.0.0 up to, but not including, 5.11.2.
- Agencies and hosts that maintain many Craft installs, including staging and forgotten legacy sites that are still reachable from the internet.
Because no login is required, exposure does not depend on how many editor accounts you have or how strong their passwords are. Whether a site is reachable matters more. The research does not say whether any configuration makes an install immune, so do not assume one does.
How to check your exposure
First find the installed Craft version. In the control panel, the version is shown in the footer and on the Utilities updates page. If you manage the project from the command line, Composer can list the installed version of the Craft package. Run this read-only command from the project root and compare the result to 4.18.9 and 5.11.2:
composer show craftcms/cmsNext, review your logs for signs of probing. The research gives no specific indicators, so look for general patterns: unusual or very long values in requests to search-related endpoints, bursts of database errors, and unexpected 500 responses. This grep counts search-related requests per day in a typical access log; adjust the path for your server:
grep -i 'search' /var/log/nginx/access.log | awk '{print $4}' | cut -d: -f1 | sort | uniq -cA spike is not proof of an attack, and a clean result does not prove safety. It only tells you where to look more closely.
What to do now
- Identify every Craft CMS install you run, including staging, dev and client sites.
- Back up the database and files before changing anything.
- Upgrade 4.x sites to 4.18.9 or later, and 5.x sites to 5.11.2 or later.
- Confirm the new version is live after deployment, not only in your repository.
- Review the admin user list for accounts you do not recognize or admin flags you did not set.
- If anything looks wrong, reset administrator passwords and rotate secrets stored in the database or environment.
- Check access and database logs for unusual search requests since before November 6, 2026.
- Restrict access to the control panel by IP or VPN where practical.
Run the update with Composer from the project root. Use the constraint that matches your major version, and review Craft's own upgrade notes for your release before applying it to production:
composer update craftcms/cmsAfterward, run composer show craftcms/cms again and confirm the version is at least 4.18.9 or 5.11.2. If your composer.json pins an older range, loosen it to permit the fixed release.
Detection and monitoring afterward
Because the described impact includes changing admin flags and password hashes, post-patch checks matter. Patching closes the hole but does not undo changes made before the update.
- Compare current admin accounts against a known-good list and look at recent account changes.
- Watch for unexpected logins, new plugins, modified templates or new files in web-accessible folders.
- Keep database and web server logs for at least several weeks so you can investigate later.
- Run an outside-in check of your public pages for injected scripts or redirects, for example with the free malware scanner, and read what outside-in detection can and cannot see.
If you suspect a compromise, follow the steps in Website hacked: what to do. For ongoing visibility into uptime, certificate and header changes across client sites, Webforta Monitor can help you notice unexpected changes sooner.
What is still unknown
- No source in the research reports active exploitation, and the CVE is not listed in CISA KEV at the time of writing. That may change.
- No public proof-of-concept is mentioned in the research.
- The Craft project advisory and VulnCheck page were not available in full, so the exact internal fix and any workarounds are not confirmed here.
- Only one independent publisher covers this so far, so details could be refined as more analysis appears.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
