On this page (7 sections)

A critical vulnerability, tracked as CVE-2026-130674, has been published for Craft CMS. According to the GitHub Advisory Database entry, Craft CMS from 5.0.0 before 5.11.4 contains an incomplete blocklist fix. Someone who can author entry type title formats may be able to write arbitrary files and reach remote code execution.

If you run a Craft CMS 5 site, or manage sites for clients that do, check your version now. Details are thin so far: the advisory is a short description, and the entry is marked unreviewed. This article covers what is stated, what is not, and what you can do today.

What was disclosed

The advisory describes an incomplete fix to an earlier blocklist. A blocklist is a list of things a feature refuses to do. When a fix only blocks some dangerous options, attackers can look for ones that were missed. Here, the advisory says attackers who can author entry type title formats can write arbitrary files using the ZipArchive or XMLWriter classes.

The advisory also says the non-sandboxed renderObjectTemplate() renderer can be abused to write attacker-controlled content into the web docroot, which it says achieves remote code execution. The docroot is the folder your web server publishes. Content written there can be requested over HTTP, and if the server executes it, the attacker runs code on your host.

Only one primary source exists for this story. The NVD page repeats the GitHub advisory text word for word, so it is not independent confirmation. No vendor release notes, proof-of-concept or exploitation reports were available in the research.

Technical background in plain terms

Entry type title formats in Craft let administrators define how entry titles are generated from a template. Template rendering is powerful, so it is normally restricted. The advisory says this particular renderer is not sandboxed, which means template content can reach PHP classes that should be off limits. The earlier fix tried to block dangerous classes, and the advisory says it was incomplete.

The weakness class is a bypassed denylist leading to arbitrary file write. This kind of flaw is serious because a written file in a public folder usually becomes code execution. We are not publishing, and the sources do not provide, any exploit detail.

Severity scores differ

The CVE record lists a CVSS score of 9.8. The GitHub advisory page shows a CVSS v4 base score of 9.3, with network attack vector, low complexity, no privileges required and no user interaction. That is odd, because the description says the attacker must be able to author entry type title formats, which suggests some level of access. The sources do not explain the gap, so treat the exact privilege requirement as unclear. Either way, plan to patch quickly.

Who is realistically exposed

  • Any site running Craft CMS 5.0.0 up to, but not including, 5.11.4.
  • Sites with several editors, agency staff or contractors who have permission to change entry types, since the attacker needs to author title formats.
  • Sites where a low-trust account could be taken over, for example through reused or phished credentials.
  • Hosts where the web server user can write to the docroot, which the advisory's attack path relies on.

Craft 4 and earlier are not mentioned in the advisory. Do not assume they are safe or affected; check the vendor's release notes for your branch.

How to check your exposure

First find your installed Craft version. Run this from the project root on the server. It prints the installed Craft CMS version. You are looking for a number below 5.11.4 within the 5.x line.

Show the installed Craft CMS version (run from the project root)Shell
php craft --version

If you manage the project with Composer, this read-only command shows the locked version of the package from composer.lock.

Show the installed craftcms/cms package version (run from the project root)Shell
composer show craftcms/cms

You can also see the version in the Craft control panel utilities area. Next, review who can change entry types and fields, since that is the access the advisory describes.

What to do now

  1. Back up the database and files, and note your current Craft version.
  2. Update Craft CMS to 5.11.4 or later, following the vendor's update guidance and testing on staging first where you can.
  3. Review which accounts can edit entry types, and remove that permission from anyone who does not need it.
  4. Reset passwords and enable two-step verification for administrator and editor accounts.
  5. Check the web docroot for files you do not recognize, especially recently modified PHP files or archives.
  6. Make sure the web server user cannot write to directories that are served and executed, where your setup allows it.
  7. Review access and application logs for unexpected requests to new files and for edits to entry type settings.
  8. If you find unknown files, treat the site as compromised and follow an incident process before simply restoring.

This command updates the package through Composer. Run it on a staging copy first.

Caution. Updating a CMS can change behavior and may require database migrations. Back up first, test on staging, and plan a short maintenance window for production.
Update Craft CMS with Composer (run from the project root, after a backup)Shell
composer update craftcms/cms

Then check the version again with the command above and confirm it reports 5.11.4 or higher. Note that Composer will only move to versions allowed by your composer.json constraint, so adjust it if the update does not reach 5.11.4.

To look for recently changed files in the docroot, this read-only command lists PHP files modified in the last 14 days. Replace the path with your web root and compare results with your deployment history.

List recently modified PHP files under the web root (read-only)Shell
find /path/to/web -type f -name '*.php' -mtime -14

Detection and monitoring afterwards

A file written into the docroot is the kind of change you can catch if you watch for it. Keep deployments in version control so any file that is not in your repository stands out. Consider file integrity monitoring on the web root, and alert on new executable files in upload or asset folders.

From the outside, you can also keep an eye on your site's headers, certificate and unexpected changes using tools such as Webforta Monitor, and run a free malware scan for a quick check. Outside-in checks have limits, as explained in what outside-in malware detection can and cannot see, so they complement server-side review and do not replace it.

If you suspect a compromise, the guide on what to do when a website is hacked walks through containment and cleanup.

What is still unknown

  • Whether the vendor has published release notes or a separate advisory with more detail. The research only included the GitHub entry and NVD.
  • Whether the issue is being exploited. No reports were found.
  • The exact privileges needed, given the gap between the description and the CVSS metrics.
  • Whether versions outside the 5.x line are affected.

We will treat this as developing. Check the advisory and the Craft CMS release notes for updates, and apply 5.11.4 or later without waiting for more detail.

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.

  1. CVE-2026-130674 - GitHub Advisory Databasegithub.com
  2. CVE-2026-130674: Craft CMS from 5.0.0 before 5.11.4 contains an incomplete blocklist fix that allows attackers who can author entry type title formats to write arbitrary files…nvd.nist.gov ·
  • Craft CMS
  • CVE-2026-130674
  • RCE
  • CMS security
  • patching