The AI Engine WordPress plugin before 3.5.5 does not sanitize a user-supplied filename before using it to write a downloaded file, allowing authenticated users with editor-level access to write attacker-controlled bytes to an arbitrary location on the server via path traversal.
Casky was already ahead
This CVE exploits attack patterns that Casky's 0matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.
The AI Engine WordPress plugin before version 3.5.5 contains a critical path traversal vulnerability in its file download functionality. Attackers with editor-level WordPress access can exploit unsanitized filename parameters to write arbitrary files to any location on the server filesystem. This vulnerability matters because WordPress editor accounts are common targets for compromise, and successful exploitation enables attackers to overwrite critical system files, inject malicious code into web-accessible directories, or establish persistent backdoors. Affected organizations running vulnerable versions of this popular AI integration plugin face risks ranging from website defacement to complete server compromise, making this a high-priority patch for any WordPress installation using AI Engine.
While Casky's 754 security skills do not currently map directly to this specific CVE, practitioners leveraging Claude AI's extended reasoning capabilities would detect the attack patterns through analysis of file system operations and access control violations. The vulnerability aligns with MITRE ATT&CK techniques including T1190 (Exploit Public-Facing Application) for initial access and T1547 (Boot or Logon Autostart Execution) if attackers write to startup directories. Security practitioners would identify suspicious findings including: unexpected file creation outside intended directories, path traversal sequences in request logs (../ patterns), and write operations by authenticated users to sensitive locations like wp-content/plugins or system directories. Detection would focus on monitoring editor-level user file operations, validating filename sanitization in plugin code reviews, and flagging any unauthorized filesystem writes during incident investigation.
Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →
Casky has 0 skills that investigate the attack patterns behind CVE-2026-12511. Run one and get CVSS-scored findings in 3 minutes.
Run the skill that detects this →© 2026 Casky.AI, Inc. · AI Security Investigation