Skip to content
Web

CVE-2026-15802

8.1
High
EPSS 0.82%Patch availableJul 23, 2026

Authenticated WordPress plugin flaw allows arbitrary file deletion and potential RCE.

common questions

Is CVE-2026-15802 being exploited?

Not confirmed. CVE-2026-15802 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.82% probability of exploitation in the next 30 days.

How severe is CVE-2026-15802?

CVE-2026-15802 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-15802?

Yes. A fix has been recorded for CVE-2026-15802. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-15802 affect?

CVE-2026-15802 affects WP Foodbakery plugin (<=4.9), WordPress sites using Foodbakery, PHP web servers hosting affected sites. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-15802?

Update to patched version (>4.9) or remove plugin; restrict low‑privilege accounts and scan for tampering.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
WP Foodbakery plugin (<=4.9)WordPress sites using FoodbakeryPHP web servers hosting affected sites
impact

Authenticated (subscriber+) attackers can delete arbitrary server files via path-traversal, enabling RCE by removing critical files (e.g., wp-config.php).

action required

Immediate action required

affected versions
Chimpstudio WP Foodbakery
  • affected<= 4.9

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free