CVE-2026-6433
Arbitrary PHP Code Execution in Custom css-js-php WordPress Plugin
Publication date: 2026-05-11
Last updated on: 2026-05-11
Assigner: WPScan
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| custom_css_js_php | custom_css_js_php | to 2.0.7 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability impact me? :
This vulnerability allows attackers to execute arbitrary PHP code on your server without needing to authenticate.
Such remote code execution can lead to full compromise of the affected server, including data theft, data loss, defacement, or using the server as a launchpad for further attacks.
Because the attacker can run any PHP code, they could install malware, create backdoors, or disrupt your website's operation.
Can you explain this vulnerability to me?
The vulnerability CVE-2026-6433 affects the WordPress plugin "Custom CSS JS PHP" version 2.0.7 or below.
It occurs because the plugin does not properly sanitize user input before using it in a SQL query.
The result of this query is then passed to the eval() function, which allows unauthenticated users to execute arbitrary PHP code on the server.
This is essentially a remote code execution (RCE) vulnerability exploitable without authentication.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves identifying if the WordPress site is running the Custom CSS JS PHP plugin version 2.0.7 or below, as these versions are vulnerable.
Since the vulnerability allows unauthenticated SQL injection leading to remote code execution, monitoring for unusual or suspicious HTTP requests targeting the plugin endpoints may help detect exploitation attempts.
Specific commands or automated tools to detect this vulnerability are not provided in the available resources.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include disabling or removing the Custom CSS JS PHP plugin version 2.0.7 or below from your WordPress installation to prevent exploitation.
Since the vulnerability remains unpatched as of the last update, avoid using the vulnerable plugin until a fixed version is released.
Additionally, monitor your server logs for any suspicious activity and consider implementing web application firewall (WAF) rules to block malicious requests targeting this plugin.