Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-45293 high CVSS 8.6

Vulnerability in wp-coding-standards/wpcs (CVE-2026-45293)

Summary

Vulnerability in wp-coding-standards/wpcs (CVE-2026-45293). Successful exploitation can lead to full system takeover. Exploitable via WordPress.WP.EnqueuedResourceParameters. Mitigation: upgrade to 3.4.1 or later.

Original description

The description as published by the source.

Impact

WordPress Coding Standards (WordPressCS) versions before 3.4.1 contain an arbitrary code execution vulnerability in the WordPress.WP.EnqueuedResourceParameters sniff. As a result, running PHPCS with WordPressCS over untrusted PHP code, for example, in a CI pipeline that lints pull requests, or on a developer machine reviewing third-party code, could lead to arbitrary command execution on the scanning host.

This affects users of the WordPress and WordPress-Extra rulesets. The WordPress-Core ruleset and the WordPress-Docs ruleset are not affected.

The vulnerability happens when the sniff checks whether the $var argument passed to functions such as wp_enqueue_script() or wp_register_script() evaluates to a falsy value. The sniff's is_falsy() method reconstructed the argument and ran it through eval(). Because of this, a maliciously crafted $ver argument such as 'system'('id') would be executed during the scan.

Patches

This issue has been fixed in WordPressCS 3.4.1. We recommend all users upgrade to 3.4.1 or later.

Workaround

Users of the WordPress and WordPress-Extra rulesets, who cannot upgrade immediately, can disable the affected sniff by adding an tag to their custom ruleset (the ref value might vary depending on the ruleset):

To verify that the sniff has been disabled, run PHPCS with the -e flag, which lists all the sniffs a standard will run. WordPress.WP.EnqueuedResourceParameters should no…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-45293 has been found in wp-coding-standards/wpcs.
Attackers can target a specific entry point like WordPress.WP.EnqueuedResourceParameters over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.6/10.
What to do: upgrade wp-coding-standards/wpcs to 3.4.1 or later.
If unsure, ask your IT team or search "wp-coding-standards/wpcs CVE-2026-45293" on the vendor's site.

CVE-2026-45293 (wp-coding-standards/wpcs) — CWE-95 / CVSS v3 8.6
Attack vector: local / unauthenticated
Attack surface: WordPress.WP.EnqueuedResourceParameters / WordPress / ref
Patched: 3.4.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-95) exists in wp-coding-standards/wpcs. Attackers reach the vulnerable code path via WordPress.WP.EnqueuedResourceParameters without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of wp-coding-standards/wpcs. Attack surface: WordPress.WP.EnqueuedResourceParameters / WordPress / ref.

🔥 Severity

Severity: High (CVSS 8.6/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 3.4.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'wp-coding-standards/wpcs' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'wp-coding-standards/wpcs' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で wp-coding-standards/wpcs を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade wp-coding-standards/wpcs to 3.4.1

    ステージング環境で 3.4.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

composer wp-coding-standards/wpcs
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.4.1"}]}]
Packagist wp-coding-standards/wpcs
[{"type":"ECOSYSTEM","events":[{"introduced":"0.14.1"},{"fixed":"3.4.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details