CVE-2026-45293Disclosure

LOWCVSS 8.6 · HIGH

Signal is active with 1 mentions in latest observed window

Immediate actions

Patch affected systems immediately

Recommended action window: Monitor and triage in normal cycle

NVD description

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.

Back to dashboard

0.5/ 10 priority

Sources & remediation

Other references

Weakness type (CWE)

CWE-95

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

AVAILABLE

Momentum

STABLE

Threat summary

Patch or workaround signal is available
3 mentions across 2 observed days
Momentum state: stable

What's happening

Patch or workaround mentioned in 2 signals
Technical details provided in 3 signals
Disclosure: 2 classified signals
Peaked 1d ago at 2 mentions (2026-07-29); latest day: 1
3 total mentions across 2 days

Deep dive

Activity timeline3 mentions / 2d

Signal classification2 categories

Disclosure

266.7%

Patch

133.3%

Referenced assets2 URLs

By indicator

Classification over time

Date	Total	Labels

2026-07-29	2	Disclosure1Patch1
2026-07-30	1	Disclosure1

Full discourse3 posts

Daily CyberSecurity@Daily_CyberSec91d
Patch
CVE-2026-45293 is an arbitrary code execution flaw in WordPress Coding Standards, rated CVSS 8.6. The dev tool has 46M+ installs. Upgrade to 3.4.1. #WordPressCS #CVE202645293 #WordPress #CodeExecution #PHPCS #DevSecOps #SupplyChain #InfoSec #CyberSecurity http://securityonline.info/wordpresscs-cve-2026-45293/
Post summary
A CVE for arbitrary code execution in WordPress Coding Standards is reported; the advisory advises upgrading to version 3.4.1 to mitigate the high‑severity flaw.
00110421
12.6K followersView on X
キタきつね@foxbook90d
Disclosure
CVE-2026-45293：4900万回以上インストールされているツール、WordPressコーディング標準における任意のコード実行の脆弱性 CVE-2026-45293: Arbitrary Code Execution in WordPress Coding Standards, a Tool With 49M+ Installs #DailyCyberSecurity (Jul 29) https://securityonline.info/wordpresscs-cve-2026-45293/
Post summary
The post announces CVE‑2026‑45293, highlighting arbitrary code execution in WordPress coding standards, but provides no PoC, exploit code, patch, or evidence of active exploitation.
00010294
4.9K followersView on X
ByteDrop@ByteDrop45391d
Disclosure
Run a WordPress site with the Coding Standards plugin? It has 49 million installs and a fresh critical flaw, CVE-2026-45293, letting arbitrary code execution. That's not a niche plugin nobody's heard of. That's a dev tool sitting quietly on an enormous share of the WordPress ecosystem, unauthenticated exploitation possible if you haven't patched. Check your plugin version before you check anything else today. #cybersecurity #wordpress
Post summary
A critical vulnerability (CVE‑2026‑45293) in the WordPress Coding Standards plugin allows arbitrary code execution; users are urged to patch or update to prevent potential exploitation.
1000024
26 followersView on X

Explore more

Back to dashboard