Security readout for executives and security teams
Plain-English summary
An unauthenticated attacker can place a malicious file path into a SigmaForms Pro upload field. If an administrator later deletes that submission, the plugin may delete an arbitrary server file. Loss of a critical WordPress file could disrupt the site or create conditions for code execution.
Executive priority
Treat this as an immediate remediation priority for internet-facing WordPress sites using the affected plugin. Rapid inventory, containment, and vendor-guided updating are warranted because a routine administrator action can trigger destructive file deletion. Escalate any suspicious submission paths or missing files to incident response.
Technical view
SigmaForms Pro through version 1.4.11 reportedly fails to validate paths in delete_submission_files, enabling stored path traversal through a form upload field. The dangerous deletion occurs later when an administrator deletes the submission. The cited assessment is CVSS 3.1 9.8 and CWE-22. Code execution is a potential consequence, not evidence of exploitation.
Likely exposure
WordPress sites running SigmaForms Pro version 1.4.11 or earlier are potentially exposed, particularly where unauthenticated users can submit forms containing upload fields. Exploitation also depends on an administrator deleting the attacker-controlled submission. The bundle’s structured affected-version entry is inconsistent, so administrators should confirm scope with the vendor.
Exploitation context
The source bundle does not report known active exploitation, and the CVE is not identified as being in CISA KEV. The attack is unauthenticated but has a delayed administrative trigger. Arbitrary deletion could cause outage, configuration loss, or potentially code execution when a security-critical file is removed.
Researcher notes
The vulnerability is described as stored path traversal in delete_submission_files. Attacker input enters through an unauthenticated upload field, while deletion is triggered by later administrative record removal. This interaction should inform testing and log correlation. The supplied structured affected data conflicts with the narrative version range, and no confirmed patched version is named.
Mitigation direction
- Identify and prioritize every site running SigmaForms Pro 1.4.11 or earlier.
- Check BDThemes guidance for a confirmed fixed release, then update promptly.
- Temporarily disable the plugin or affected public forms where operationally acceptable.
- Avoid deleting suspicious submissions until their stored file paths are safely reviewed.
- Maintain tested backups of WordPress files, configuration, and databases.
Validation and detection
- Confirm the installed plugin version on every WordPress instance.
- Inventory public SigmaForms forms containing file upload fields.
- Review stored submission paths for unexpected absolute or parent-directory references.
- Check WordPress file integrity and investigate missing or recently deleted critical files.
- Verify backups can restore application files, configuration, and database content.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-78657 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9WordfenceVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- Source timelineWordfence
Vendor Notified
- Source timelineWordfence
Disclosed
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/c714e2b3-8a96-4078-99a4-4ce620939828?source=cveCVE reference, Wordfence
- https://feedback.bdthemes.com/announcementsCVE reference, Wordfence
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.