CVE-2026-16230: Formidable Digital Signatures <= 3.0.6 - Unauthenticated Arbitrary File Deletion via Signature Field
The Formidable Digital Signatures plugin for WordPress is vulnerable to file deletion due to insufficient file path validation in the delete_file function in all versions up to, and including, 3.0.6. This makes it possible for unauthenticated attackers to delete files on the server by supplying an attacker-controlled filename in the item_meta[field_id][content] parameter alongside the delete_saved_image flag during the standard entry-creation POST flow on any form that accepts anonymous submissions.
Security readout for executives and security teams
Plain-English summary
An unauthenticated attacker may delete server files through a publicly submitable WordPress form using Formidable Digital Signatures 3.0.6 or earlier. Deleted files could disrupt the website and potentially undermine its integrity or confidentiality. The CVSS score is 9.8, but the supplied sources do not establish active exploitation.
Executive priority
Treat internet-facing affected sites as an immediate remediation priority. Rapidly identify exposed anonymous signature forms, update the plugin, and check file integrity. Escalate incident response if unexplained deletions or suspicious submissions are found.
Technical view
Insufficient path validation in the plugin’s delete_file function allows attacker-controlled filename input during entry creation when delete_saved_image is set. Exploitation requires a form accepting anonymous submissions. The issue is classified as CWE-23 path traversal and affects versions through 3.0.6 according to the narrative record.
Likely exposure
Highest exposure exists on internet-facing WordPress sites running version 3.0.6 or earlier with anonymous forms using signature fields. Sites without the plugin, outside the stated version range, or without anonymous submission paths are not shown to be exploitable by the supplied evidence.
Exploitation context
The reported attack is remote, unauthenticated, low complexity, and requires no user interaction. It can occur through the normal form entry-creation flow. CISA KEV status is false, and the supplied bundle provides no evidence of active exploitation in the wild.
Researcher notes
The narrative, title, and CVSS vector support critical severity. However, the structured affected entry lists version "0" with defaultStatus "unaffected," conflicting with the stated affected range through 3.0.6. Validate version status against vendor and CVE updates. No exploit-in-the-wild evidence is supplied.
Mitigation direction
Upgrade Formidable Digital Signatures to version 3.1 or a later vendor-supported release.
Temporarily disable affected signature forms or anonymous submissions until the update is verified.
Back up critical site files and confirm backups are protected from web-server deletion.
Review current vendor and Wordfence guidance for additional mitigations or revised affected-version information.
Validation and detection
Inventory WordPress sites for Formidable Digital Signatures and record installed versions.
Identify public forms accepting anonymous submissions and determine whether they contain signature fields.
Confirm affected installations run version 3.1 or a later vendor-supported release.
Review web, application, and file-integrity logs for suspicious form submissions or unexpected deletions.
Verify critical WordPress and server files against trusted backups or deployment artifacts.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · medium confidence lookup
CWE-23: 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.
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.
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.
1CVSS vectors
5Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-23 · source CWE mapping
Relative Path Traversal
Relative Path Traversal represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.