Skip to content
Fencer Intel
high 7.4

CVE-2026-115826 json

Multi Step for Contact Form 7 <= 2.9.1 - Insecure Direct Object Reference to Unauthenticated Arbitrary Submission Deletion via '_cf7mls_db_form_data_id' Parameter

published 13h ago modified 11h ago also EUVD-2026-128842

cvss
7.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
—
no EPSS score yet
public exploits
0
none known

Summary

The Multi Step for Contact Form 7 plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 2.9.1 via the '_cf7mls_db_form_data_id' parameter due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to permanently delete arbitrary stored Contact Form 7 submissions from the database. Exploitation requires the companion CF7 Database plugin to be active and the per-form "Save every step, not just the final submission" option to be enabled.

Is CVE-2026-115826 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
12h ago

CVSS scores

assigned by version score vector
CNA 3.1 7.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H

Affected products

  • ninjateam Multi Step for Contact Form 7

Classification

Weakness
  • CWE-639 Authorization Bypass Through User-Controlled Key
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.