CVE-2026-126716 json
Mega Forms <= 1.7.9 - Unauthenticated Arbitrary File Deletion via Submitted Field Value
published yesterday modified yesterday also EUVD-2026-131407
- cvss
- 8.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 72%
- public exploits
- 0
- none known
Summary
The Mega Forms – Drag & Drop Form Builder with Multi-Step & Conditional Logic plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the delete_entry function in all versions up to, and including, 1.7.9 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). The attacker-supplied path is stored via the unauthenticated form submission endpoint, but the actual file deletion only occurs when an administrator subsequently deletes the stored entry — a routine housekeeping action that serves as the detonation trigger. Successful exploitation additionally requires an action by an administrator — the attacker cannot trigger the vulnerability on their own.
Is CVE-2026-126716 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 FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- yesterday
Exploit prediction
1.35% chance of exploitation in the next 30 days, higher than 72% of all scored CVEs (FIRST EPSS, 2026-11-21).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H |
Affected products
- alikhallad Mega Forms – Drag & Drop Form Builder with Multi-Step & Conditional Logic
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/c378777b-77a6-4d85-8933-a037bf368904?source=cve
- plugins.trac.wordpress.org /browser/mega-forms/tags/1.7.8/common/partials/class-mega-forms-api.php#L1303
- plugins.trac.wordpress.org /browser/mega-forms/tags/1.7.8/common/partials/class-mega-forms-files-api.php#L544
- plugins.trac.wordpress.org /browser/mega-forms/tags/1.7.8/public/partials/class-mega-forms-public-ajax.php#L20
- plugins.trac.wordpress.org /browser/mega-forms/tags/1.7.8/common/partials/class-mega-forms-submit.php#L237
- plugins.trac.wordpress.org /browser/mega-forms/tags/1.7.8/common/partials/form/fields/base/class-mega-forms-field.php#L1511
- plugins.trac.wordpress.org /browser/mega-forms/tags/1.7.8/common/partials/class-mega-forms-api.php#L1479
- plugins.trac.wordpress.org /changeset/1234567/mega-forms
- plugins.trac.wordpress.org /changeset/3810140/mega-forms/trunk/common/partials/class-mega-forms-api.php
Sources
- CVE List CVE-2026-126716
- NVD CVE-2026-126716
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.