Skip to main content
VulnerabilityPublished Updated

CVE-2026-9843: Database for Contact Form 7, WPforms, Elementor forms (WordPress plugin) · Path Traversal

Affects Database for Contact Form 7, WPforms, Elementor forms (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.1 High.

Data as of 2 Nov 2026, 10:58 UTC

CVSS 3.1 base score
8.1High
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:N/UI:R/S:U/C:N/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 2 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
crmperksDatabase for Contact Form 7, WPforms, Elementor formsAffected
  • <=1.5.1
Fixed in–

AI-suggested

Until an official fix is available, restrict administrator access to trusted users only and avoid viewing or editing suspicious form entries. Monitor for updates from the crmperks vendor regarding patches or official mitigations.

Description

The Database for Contact Form 7, WPforms, Elementor forms plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the view_page function in all versions up to, and including, 1.5.1. This makes it possible for unauthenticated attackers to 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). Successful exploitation requires an administrator to view or edit the poisoned form entry, at which point PHP's bracket parser reshapes the attacker-crafted JSON key to bypass the stored-path isset check and trigger deletion of the traversal-specified file.

References

Community reviews

Loading reviews…