# CVE-2026-6433: Custom CSS JS PHP <= 2.0.7 - Unauthenticated SQL Injection to RCE

> Unauthenticated attackers can exploit SQL injection to execute arbitrary PHP code via eval in the Custom CSS JS PHP plugin.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 May 2026
- **Updated:** 11 May 2026
- **Also known as:** GHSA-c697-h8w8-m356

## What is CVE-2026-6433?

CVE-2026-6433 is a high-severity SQL injection vulnerability in Unknown Custom css-js-php, published on 11 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Custom css-js-php WordPress plugin through 2.0.7 does not properly sanitize user input before using it in a SQL query, and the result is passed to eval(), allowing unauthenticated users to execute arbitrary PHP code on the server.

## Which versions are affected by CVE-2026-6433?


## How do I fix CVE-2026-6433?

No fix has been published for CVE-2026-6433 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-6433 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-6433 exists.

Public exploit code:

- PoC for CVE-2026-6433: WordPress FlipperCode Custom CSS, JS & PHP (≤2.0.7) — unauthenticated SQLi to RCE. Python 3 stdlib; single target or bulk multi-threaded scanning. Authorized testing & research only. (github_poc): https://github.com/murrez/CVE-2026-6433
- FlipperCode Custom CSS, JS & PHP <= 2.0.7 - Remote Code Execution (nuclei): http/cves/2026/CVE-2026-6433.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-6433 and fix it if it is affected.

What it is: CVE-2026-6433 is a high-severity SQL injection vulnerability in Unknown Custom css-js-php, published on 11 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-6433 exists.

Affected product: Unknown Custom css-js-php. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-6433/ (Markdown: https://insights.sbomify.com/CVE-2026-6433/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-6433
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-6433
- OSV: https://osv.dev/vulnerability/CVE-2026-6433

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-6433/
Summaries are generated and may contain mistakes; the official description above is the record.