Skip to content

CVE-2026-45293 — WordPress Coding Standards is a set of PHP_CodeSniffer rules (sniffs) that enforce…

Key facts

CVE-2026-45293 is a High (8.6) vulnerability: WordPress Coding Standards is a set of PHP_CodeSniffer rules (sniffs) that enforce…. This entry ships a detection-only PoC and a Docker test lab.

CVE CVE-2026-45293
Severity High (8.6)
Detection / prevention —
PoC poc.py
Source 2026/CVE-2026-45293/

Details

English | 한국어

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.

Vulnerability Details

Property Value
CVE ID CVE-2026-45293
Type RCE
CVSS Score 8.6

Proof of Concept

Download

# Download PoC script
curl -O https://raw.githubusercontent.com/fankh/vulnerability-poc/main/2026/CVE-2026-45293/poc.py

Usage

# Run PoC against target
python3 poc.py --target <TARGET_URL>

# With authentication
python3 poc.py --target <TARGET_URL> --username <USER> --password <PASS>

⚠️ Warning: This PoC is for authorized security testing only. It uses detection-only techniques and does not exploit or damage target systems.

Test Lab

This repository includes a Docker-based test environment with both vulnerable and patched applications.

Quick Start

# Clone and navigate to CVE directory
cd CVE-2026-45293

# Start both applications
docker-compose up -d

# Run tests
./run-tests.sh    # Linux/Mac
./run-tests.ps1   # Windows PowerShell

Application Endpoints

Application URL Status
Vulnerable App http://localhost:8080 Shows vulnerability
Patched App http://localhost:8081 Demonstrates fix

Directory Structure

├── README.md           # English documentation
├── README_KO.md        # Korean documentation
├── poc.py              # PoC detection script
├── docker-compose.yml  # Container orchestration
├── run-tests.sh        # Linux/Mac test runner
├── run-tests.ps1       # Windows test runner
├── vulnerable-app/     # Vulnerable version
│   ├── app.py
│   ├── Dockerfile
│   └── requirements.txt
└── patched-app/        # Fixed version
    ├── app.py
    ├── Dockerfile
    └── requirements.txt

References

  • https://github.com/WordPress/WordPress-Coding-Standards/commit/a29048d0bbef5cf25d42349c74e4072d3cbc8325
  • https://github.com/WordPress/WordPress-Coding-Standards/pull/2771
  • https://github.com/WordPress/WordPress-Coding-Standards/releases/tag/3.4.1
  • https://github.com/WordPress/WordPress-Coding-Standards/security/advisories/GHSA-3pwp-g2mj-5p3v

Generated by PoC Generator on 2026-08-03T14:06:15.091348063

Frequently asked questions

What is CVE-2026-45293?

CVE-2026-45293 is a High (8.6) vulnerability: WordPress Coding Standards is a set of PHP_CodeSniffer rules (sniffs) that enforce…. This entry ships a detection-only PoC and a Docker test lab.

How do I detect CVE-2026-45293?

Run the detection-only PoC included with this entry against your Docker test lab to confirm whether a target is affected; pair it with your own IDS logging.

How do I block or mitigate CVE-2026-45293?

Upgrade to a fixed version per the vendor advisory; the NVD record lists the affected versions. Use the included PoC to verify your remediation.


For authorized security testing and research only. See the full source and NVD record.