p PatchFirst

CVE-2026-45293

CVE-2026-45293 · WordPress Coding Standards (WordPressCS) contains an arbitrary code execution vulnerability

This page contains facts from public vulnerability sources. Check the original advisory before updating.

WordPress Coding Standards is a set of PHP_CodeSniffer rules (sniffs) that enforce WordPress coding conventions. From 0.14.1 until 3.4.1, the WordPress.WP.EnqueuedResourceParameters sniff (active in the WordPress and WordPress-Extra rulesets) reconstructed the $ver argument passed to functions such as wp_enqueue_script() and ran it through eval() inside its is_falsy() method, so a maliciously crafted argument such as 'system'('id') would execute during a scan; as a result, running PHPCS with WordPressCS over untrusted PHP (for example a CI pipeline that lints pull requests, or a developer reviewing third-party code) could lead to arbitrary command execution on the scanning host. The WordPress-Core and WordPress-Docs rulesets are not affected. This issue is fixed in version 3.4.1.

CVSS 8.6 · High · EPSS 0.2% · Fix available

Published
Updated

Stack: php

Affected products and versions

  • wordpress-coding-standards

    Versions
    • >= 0.14.1, < 3.4.1: Affected

    No fix published

  • wp-coding-standards/wpcs Packagist

    Versions
    • 0.14.1
    • 1.0.0
    • 1.1.0
    • 1.2.0
    • 1.2.1
    • 2.0.0
    • 2.0.0-RC1
    • 2.1.0
    • 2.1.1
    • 2.2.0
    • 2.2.1
    • 2.3.0
    • 3.0.0
    • 3.0.1
    • 3.1.0
    • 3.2.0
    • 3.3.0
    • 3.4.0
    Affected ranges
    • ECOSYSTEM: ≥ 0.14.1, < 3.4.1

    Update to 3.4.1

Original sources

Check your server →