CVE-2024-7777VulnerabilityPublished 20 Aug 2024

CVE-2024-7777: Contact Form by Bit Form: Multi Step Form, Calculation Contact Form, Payment Contact Form & Custom Contact Form builder (WordPress plugin) · Path Traversal

Affects Contact Form by Bit Form: Multi Step Form, Calculation Contact Form, Payment Contact Form & Custom Contact Form builder (WordPress plugin)Source CVE Database V5

Not known to be exploited · CVSS 9.0 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

9.0Critical

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 1.0% chance of exploitation in 30 days – higher than 63% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:H/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Changed
Confidentiality: Low
Integrity: High
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Aug 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
bitpressadmin Contact Form by Bit Form: Multi Step Form, Calculation Contact Form, Payment Contact Form & Custom Contact Form builder	Affected =2.0	Fixed in–

AI-suggested

Organizations should immediately audit their WordPress installations to identify the presence of the vulnerable 'Contact Form by Bit Form' plugin versions 2.0 to 2.13.9. Until an official patch is released, administrators should consider disabling or uninstalling the plugin to eliminate the attack surface. Restrict administrator access strictly to trusted personnel and enforce strong authentication mechanisms such as multi-factor authentication to reduce the risk of privilege abuse. Implement file integrity monitoring to detect unauthorized file deletions or modifications, especially for critical files like wp-config.php. Regularly back up WordPress files and databases to enable rapid recovery in case of exploitation. Monitor logs for suspicious file access or deletion activities. Once a patch is available, apply it promptly. Additionally, consider deploying web application firewalls (WAFs) with custom rules to detect and block path traversal attempts targeting this plugin. Educate administrators about the risks of excessive privileges and the importance of plugin security hygiene.

Description

The Contact Form by Bit Form: Multi Step Form, Calculation Contact Form, Payment Contact Form & Custom Contact Form builder plugin for WordPress is vulnerable to arbitrary file read and deletion due to insufficient file path validation in multiple functions in versions 2.0 to 2.13.9. This makes it possible for authenticated attackers, with Administrator-level access and above, to read and delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php).

Impact

This vulnerability poses a severe risk to organizations running WordPress sites with the affected plugin. An attacker with administrator access can read sensitive files, potentially exposing credentials, configuration details, or other confidential data. More critically, the attacker can delete arbitrary files, including core WordPress configuration files like wp-config.php, which can disrupt site availability and enable remote code execution. This can lead to full server compromise, data breaches, defacement, or persistent backdoors. The impact extends to data confidentiality, integrity, and availability, potentially affecting customer trust, regulatory compliance, and business continuity. Since WordPress powers a significant portion of websites globally, any site using this plugin is at risk, especially those with multiple administrators or weak internal access controls. The absence of known exploits in the wild currently reduces immediate risk but does not diminish the urgency for remediation, as attackers may develop exploits rapidly once details are public.

Summary

CVE-2024-7777 is a path traversal vulnerability classified under CWE-22, found in the 'Contact Form by Bit Form' WordPress plugin, specifically versions 2.0 through 2.13.9. The flaw arises from improper validation of file path inputs in multiple plugin functions, allowing authenticated users with Administrator or higher privileges to manipulate file paths beyond the intended restricted directories. This enables attackers to arbitrarily read and delete files on the web server. The ability to delete critical files such as wp-config.php can lead to remote code execution by destabilizing the WordPress environment or triggering fallback behaviors that allow code injection or execution. The vulnerability does not require user interaction but does require elevated privileges, limiting exploitation to users who already have significant access. The CVSS v3.1 base score is 9.0, reflecting network attack vector, low attack complexity, high privileges required, no user interaction, and a scope change with partial confidentiality loss but high integrity and availability impact. No public exploits have been reported yet, but the risk is substantial given the potential for server compromise. The vulnerability was publicly disclosed on August 20, 2024, and no official patches have been linked yet, emphasizing the need for immediate mitigation.

CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #6OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
Implementation · Input Validation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174).
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.3.1 (opens in a new tab)
Attack patterns
Path Traversal (opens in a new tab)
Using Slashes and URL Encoding Combined to Bypass Validation Logic (opens in a new tab)
Manipulating Web Input to File System Calls (opens in a new tab)
Using Escaped Slashes in Alternate Encoding (opens in a new tab)
Using Slashes in Alternate Encoding (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Feb 2026, 01:58 UTC

WeaknessesCWE-22

Technical details

References

Community reviews

Related threats