Skip to content
Web

CVE-2026-78657

9.8
Critical
EPSS 0.72%Patch availableSep 2, 2026

Unauthenticated path traversal in SigmaForms Pro plugin allows arbitrary file deletion and potential RCE.

common questions

Is CVE-2026-78657 being exploited?

Not confirmed. CVE-2026-78657 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.72% probability of exploitation in the next 30 days.

How severe is CVE-2026-78657?

CVE-2026-78657 is rated Critical with a CVSS score of 9.8. 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-78657?

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

What does CVE-2026-78657 affect?

CVE-2026-78657 affects SigmaForms Pro – AI Generated Forms plugin <=1.4.11, WordPress sites using the plugin, Web server filesystem (webroot). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-78657?

Update to patched version (>1.4.11) or remove plugin; audit uploads and restore backups.

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

executive summary
technical analysis
affected
SigmaForms Pro – AI Generated Forms plugin <=1.4.11WordPress sites using the pluginWeb server filesystem (webroot)
impact

Unauthenticated attacker can upload path-traversal payloads that cause arbitrary server file deletion when an admin deletes a submission, enabling RCE (e.g., wp-config.php).

action required

Immediate action required

affected versions
bdthemes SigmaForms Pro – AI Generated Forms
  • affected<= 1.4.11

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