Severity: Critical (CVSS 9.8)
Affected Systems: Bdthemes Sigmaforms Pro – Ai Generated Forms; Wordpress Wordpress
Overview
Sigma Forms Pro
A critical vulnerability identified as CVE-2026-14494 has been disclosed.
The Sigma Forms Pro plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1.4.5 via the handle_form_submission function. This is due to the plugin dynamically granting the unfiltered_upload capability to all users during form submissions and bypassing MIME type validation when allowed_file_types is not configured. This makes it possible for unauthenticated attackers to execute code on the server. Several default pre-built templates including Job Application, Support Ticket, and Wholesale Application have file upload fields with no file type restrictions configured by design, making this vulnerability immediately exploitable upon installation.
Risk
CVSS and CISA data indicate the following:
- Review the OpenCVE and vendor advisory for exploit conditions and impact
OpenCVE Analysis
CVSS v4.0 N/ACVSS v3.1 9.8 CriticalCVSS v3.0 N/ACVSS v2 N/AKEV noEPSS noSSVC no
- OpenCVE title: Sigma Forms Pro <= 1.4.5 - Unauthenticated Unauthenticated Arbitrary File Upload Leading to Remote Code Execution via Pre-built Template File Upload Field
- Severity score: Critical (CVSS 9.8)
- Weaknesses: CWE-434
| Attack Vector | Network |
| Attack Complexity | Low |
| Privileges Required | None |
| User Interaction | None |
| Scope | Unchanged |
| Confidentiality Impact | High |
| Integrity Impact | High |
| Availability Impact | High |
Required Action
Review the OpenCVE detail page and linked vendor advisory, then apply the vendor-provided update or mitigation for the affected product.
Prioritize systems where the affected product is internet-facing, handles authentication, or runs with elevated privileges.
Verify Updates
Confirm whether your environment uses the affected product(s): Bdthemes Sigmaforms Pro – Ai Generated Forms; Wordpress Wordpress.
After remediation, verify the installed version against the fixed or unaffected versions listed by the vendor.
Temporary Mitigation (if patch is not available)
Use the mitigation published by the vendor. If no vendor mitigation is available, reduce exposure to the affected product, restrict access to trusted users or networks, and increase monitoring until an update can be applied.
Recommendation
- Use OpenCVE, vendor, and source references as the source of truth for affected versions and remediation
- Patch or mitigate affected products after confirming exposure in your environment
- Monitor affected systems for unusual activity until remediation is complete
Support
If you require assistance, please contact our support team.
Immediate action is strongly recommended to protect your infrastructure.
Source Details
Customer Responsibility and Backups
Before applying updates, mitigations, or configuration changes, customers should take and verify current backups or snapshots of affected systems.
Customers are responsible for managing their servers, validating their own backups, testing changes, and ensuring they can restore services if an update or mitigation causes an issue.
Saturday, August 29, 2026
