# CVE-2026-120559: Contact Form Extender for Divi Builder <= 1.0.6 - Unauthenticated Arbitrary File Deletion via Path Traversal


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 3 Nov 2026
- **Updated:** 8 Nov 2026
- **Also known as:** GHSA-93rj-fp96-fpfj

## What is CVE-2026-120559?

CVE-2026-120559 is a high-severity vulnerability in satindersingh Contact Form Extender for Divi – Submissions DB & Extra Fields, published on 3 Nov 2026. 

### Official description

The Contact Form Extender for Divi Builder plugin for WordPress is vulnerable to Arbitrary File Deletion due to insufficient file path validation in the cfefd_remove_uploaded_file() function in all versions up to, and including, 1.0.6. 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 nonce protecting this AJAX action is rendered into the public page source via wp_localize_script and is therefore retrievable by any unauthenticated visitor.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


## How do I fix CVE-2026-120559?

No fix has been published for CVE-2026-120559 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-120559 being exploited?

There is no known exploitation of CVE-2026-120559 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120559 and fix it if it is affected.

What it is: CVE-2026-120559 is a high-severity vulnerability in satindersingh Contact Form Extender for Divi – Submissions DB & Extra Fields, published on 3 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120559 in the wild and no public exploit code.

Affected product: satindersingh Contact Form Extender for Divi – Submissions DB & Extra Fields. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-120559/ (Markdown: https://insights.sbomify.com/CVE-2026-120559/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-120559
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-120559
- OSV: https://osv.dev/vulnerability/CVE-2026-120559

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-120559/
Summaries are generated and may contain mistakes; the official description above is the record.
