SigmaForms Pro WordPress Plugin Vulnerable to Arbitrary File Deletion
- Severity
- CRITICAL
- CVSS
- 9.8
- Affected component
- sigmaforms-pro (wordpress)
- Patched version
- Not yet available
An early warning has been issued for a critical vulnerability in the SigmaForms Pro WordPress plugin. Versions up to and including 1.4.11 are reportedly affected.
What happened
The SigmaForms Pro WordPress plugin, specifically versions up to and including 1.4.11, is under investigation for a critical vulnerability. This vulnerability, tracked as CVE-2026-78657, allows for arbitrary file deletion due to insufficient file path validation. If exploited, this could lead to remote code execution. The vulnerability has a CVSS score of 9.8, indicating its critical severity. There are no reports of this vulnerability being exploited in the wild at this time.
To assess your exposure, check if you are using the SigmaForms Pro plugin on your WordPress site. If so, verify the version number. Any site using version 1.4.11 or earlier is potentially vulnerable. It is recommended to review your server for any signs of unauthorized access or file changes as a precautionary measure.
What to do about it
- Monitor the primary sources for updates on a patched version.
- If you are using the SigmaForms Pro plugin, upgrade to a version beyond 1.4.11 once it becomes available.
- Review your server for any signs of unauthorized access or file changes.
- Consider disabling the plugin temporarily if an upgrade is not immediately possible and you are using a vulnerable version.
How 0Day would have caught this
sigmaforms-pro is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.
Frequently asked questions
Am I affected?
You are potentially affected if you are using the SigmaForms Pro WordPress plugin version 1.4.11 or earlier.
What should I do right now?
Monitor the primary sources for updates on a patched version. If you are using a vulnerable version, consider upgrading or disabling the plugin temporarily.
Is there a patched version available?
No official fix has been published yet. Monitor the sources for updates.
Should I review my server for any signs of compromise?
Yes, it is recommended to review your server for any signs of unauthorized access or file changes as a precautionary measure.