WooCommerce POS Plugin PHP Code Injection via Template Engine

The WCPOS – Point of Sale (POS) plugin for WooCommerce plugin for WordPress is vulnerable to Code Injection via the 'thermal' Template Engine in all versions up to, and including, 1.9.14 due to the Receipt_Renderer_Factory dispatching templates with the 'thermal' engine to the Legacy_Php_Renderer instead of a safe thermal-specific renderer. This makes it possible for authenticated attackers, with Shop Manager-level access and above, to inject arbitrary PHP code into a template post that is subsequently written to a temporary file and executed via PHP's include(), resulting in remote code execution on the server. This requires the attacker to have Shop Manager-level access or above, as the template save path enforces a wcpos_template_settings nonce and the manage_woocommerce_pos capability check.

Casky was already ahead

This CVE exploits attack patterns that Casky's 322matched 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.

Analysis

The WCPOS Point of Sale plugin for WooCommerce contains a critical code injection vulnerability in its template rendering engine. When the 'thermal' template engine is invoked, the Receipt_Renderer_Factory incorrectly dispatches templates to a legacy PHP renderer instead of a safe thermal-specific handler, allowing authenticated Shop Manager-level users to inject arbitrary PHP code into template posts. This vulnerability affects all versions up to 1.9.14 and poses a significant risk to e-commerce operations, as attackers with moderate privilege levels can achieve remote code execution on WordPress installations running vulnerable versions of this widely-used POS solution.

Casky's 322 mapped skills leverage Claude AI with extended reasoning to correlate this vulnerability across MITRE ATT&CK techniques TA0001 (Initial Access) and TA0043 (Reconnaissance). Practitioners using Casky would observe detection patterns including: suspicious template post creation or modification by Shop Manager accounts, unexpected PHP code embedded in thermal template parameters, and execution flows where user-controlled input bypasses template sanitization routines. The platform's skill coverage would flag the improper dispatcher logic (CWE-94: Improper Control of Generation of Code) through behavioral analysis of template rendering calls, privilege escalation from Shop Manager context, and post-exploitation indicators such as web shells or reverse connection attempts originating from the compromised WordPress installation.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

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 →

322 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-17581.

Abuse of Public-Facing API: Mobile API Abuse

mobile security · low

Run

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

MITRE ATT&CK Techniques

TA0001 TA0043

Investigate the attack patterns behind CVE-2026-17581

Casky has 322 skills that investigate the attack patterns behind CVE-2026-17581. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn