Skip to main content
VulnerabilityPublished

CVE-2026-6433: Custom css-js-php (WordPress plugin) · Code Injection

Affects Custom css-js-php (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · public detection template (Nuclei) · CVSS 7.3 High.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
7.3High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.1% chance of exploitation in 30 days – higher than 67% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 May 2026

  2. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Custom css-js-phpAffected
  • >=2.0.7 <=2.0.7
Fixed in–

AI-suggested

Users should monitor the vendor's advisory channels for updates and apply any official patches once available. Until then, consider disabling or removing the affected plugin version to mitigate risk.

Description

CVE-2026-6433 is a high-severity vulnerability in the Custom css-js-php WordPress plugin version 2.0.7. It arises from improper sanitization of user input before it is used in a SQL query, with the query result subsequently passed to eval(), enabling unauthenticated users to execute arbitrary PHP code on the server. This vulnerability can lead to code injection, potentially compromising the affected system's confidentiality, integrity, and availability.

References

Community reviews

Loading reviews…