CVE-2026-28695 is an authenticated remote code execution vulnerability in Craft CMS affecting 4.x and 5.x branches. The issue arises from server-side template injection in Twig where the create() Twig function exposes Craft::createObject(), allowing instantiation of attacker-controlled PHP classes with attacker-supplied constructor arguments. By combining this primitive with the bundled symfony/process dependency, an attacker can build a gadget chain that results in arbitrary command execution. The issue is described as bypassing the prior fix for CVE-2025-57811. According to the provided content, affected versions include 4.x releases introduced at 4.0.0-RC1 and 5.x releases introduced at 5.8.7; fixes are available in 4.17.0-beta.1 and 5.9.0-beta.1.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos.
The repository contains a README and one Python executable, exp.py. The script is a standalone authenticated exploit for a claimed bypass of the CVE-2026-28695 Craft CMS fix, targeting Craft CMS versions up to 5.9.8. It creates a requests session, extracts CSRF tokens from the login and dashboard pages, authenticates with supplied credentials, then sends a malicious JSON request to the element-search endpoint. The payload abuses Yii AttributeTypecastBehavior configuration and the Psy\Readline\Hoa\ConsoleProcessus::execute gadget to execute the operator-provided command. Results are intentionally blind: only the HTTP status is displayed, while timeouts are treated as potentially expected for blocking commands. The README provides a usage example that supplies a BusyBox netcat shell command, but no hardcoded remote listener, IP address, or domain is present.
The repository contains a GPL-3.0 license, a detailed README, and one Python entry point, `exploit.py`. The script uses `requests` with certificate verification disabled, establishes a Craft Control Panel session by scraping CSRF tokens from the login and dashboard pages, and sends a crafted JSON request to the element-search action. Its claimed gadget instantiates Yii `AttributeTypecastBehavior` and maps a typecast callback to `Psy\Readline\Hoa\ConsoleProcessus::execute`, aiming to reach command execution through `call_user_func()`. Execution is treated as blind because the script expects no command output and accepts an HTTP 500 response. `--check` compares baseline and `sleep 5` response times, while a supplied positional command runs a single command and `--bind` launches a configurable socat listener (default TCP/4445) executing `/bin/sh`. The script includes default credentials (`User` / `SecureP4$$!`) that can be overridden. It is a standalone operational PoC rather than a Metasploit, Nuclei, or other framework module.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.