Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-6463: CWE-73 External Control of File Name or Path in wpmudev Forminator Forms – Contact Form, Payment Form & Custom Form Builder

0
High
VulnerabilityCVE-2025-6463cvecve-2025-6463cwe-73
Published: Wed Jul 02 2025 (07/02/2025, 04:24:56 UTC)
Source: CVE Database V5
Vendor/Project: wpmudev
Product: Forminator Forms – Contact Form, Payment Form & Custom Form Builder

Description

The Forminator Forms – Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the 'entry_delete_upload_files' function in all versions up to, and including, 1.44.2. This makes it possible for unauthenticated attackers to include arbitrary file paths in a form submission. The file will be deleted when the form submission is deleted, whether by an Administrator or via auto-deletion determined by plugin settings. This can easily lead to remote code execution when the right file is deleted (such as wp-config.php).

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/26/2026, 15:37:18 UTC

Technical Analysis

CVE-2025-6463 is a vulnerability identified in the Forminator Forms plugin for WordPress, versions up to and including 1.44.2. The flaw resides in the 'entry_delete_upload_files' function, which inadequately validates file paths provided in form submissions. This insufficient validation allows an unauthenticated attacker to specify arbitrary file paths during form submission. When a form submission is deleted—either manually by an administrator or automatically via plugin settings—the specified files are deleted from the server. This arbitrary file deletion can be weaponized to remove critical WordPress files such as wp-config.php, potentially leading to remote code execution by destabilizing the application or enabling attackers to upload malicious code. The vulnerability is remotely exploitable over the network without authentication, though it requires user interaction in the form of submitting a crafted form. The CVSS v3.1 score is 8.8, reflecting high impact on confidentiality, integrity, and availability, with low attack complexity. No public exploits have been reported yet, but the risk is significant given the plugin's popularity and the critical nature of the affected files. The vulnerability is categorized under CWE-73 (External Control of File Name or Path). No official patches have been linked yet, so users must apply mitigations promptly.

Potential Impact

The impact of CVE-2025-6463 is severe for organizations running WordPress sites with the vulnerable Forminator Forms plugin. Successful exploitation can lead to arbitrary deletion of files on the web server, including critical configuration files like wp-config.php. This can cause site outages (availability impact), data breaches (confidentiality impact), and unauthorized modifications or remote code execution (integrity impact). The ability for unauthenticated attackers to trigger this via form submissions increases the attack surface, especially for public-facing websites. Organizations relying on these forms for contact, payment, or custom data collection are at risk of service disruption and compromise. The vulnerability could be exploited to deface websites, steal sensitive data, or pivot to deeper network intrusion. The lack of authentication requirement and ease of exploitation make this a high-risk threat globally, particularly for businesses with high web traffic and sensitive data processed through these forms.

Mitigation Recommendations

1. Immediately disable or restrict the deletion of form submissions in the Forminator Forms plugin until a patch is available. 2. Implement web application firewall (WAF) rules to detect and block suspicious form submissions containing file path traversal patterns or unexpected file path parameters. 3. Restrict file system permissions for the WordPress installation to prevent deletion of critical files by the web server user. 4. Monitor logs for unusual deletion activities or form submissions with suspicious payloads. 5. Educate administrators to avoid automatic deletion settings that could trigger file removals without manual oversight. 6. Regularly back up WordPress files and databases to enable quick recovery in case of file deletion. 7. Once available, promptly apply official patches from the plugin vendor. 8. Consider isolating the WordPress environment using containerization or sandboxing to limit the blast radius of potential exploitation.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-06-20T22:02:55.475Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6864b8046f40f0eb72917e7d

Added to database: 7/2/2025, 4:39:32 AM

Last enriched: 2/26/2026, 3:37:18 PM

Last updated: 3/22/2026, 3:07:24 PM

Views: 156

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses