# CVE-2026-5524: File upload in Divi Form Builder

> Unauthenticated attackers can upload executable PHP files via the acceptFileTypes parameter to achieve remote code execution on WordPress sites using Divi Form Builder.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jul 2026
- **Updated:** 2 Jul 2026
- **Also known as:** GHSA-7ch9-34jx-wqhr

## What is CVE-2026-5524?

CVE-2026-5524 is a critical vulnerability in Divi Form Builder, published on 2 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Divi Form Builder plugin for WordPress is vulnerable to Arbitrary File Upload leading to Remote Code Execution in all versions up to and including 5.1.8. This is due to insufficient file extension validation in the do_image_upload() function where user-supplied input from the acceptFileTypes POST parameter is directly interpolated into a regular expression used to validate uploaded files. Attackers can specify PHP-executable extensions such as .phtml, .phar, .php5, or .php7 to bypass the plugin's .htaccess protection which only blocks .php files specifically. Additionally, on Nginx-based servers, the .htaccess protection is completely ineffective as Nginx does not process .htaccess files. This makes it possible for unauthenticated attackers (who can obtain a nonce from any public page containing a form) to upload executable PHP files to the publicly accessible /wp-content/uploads/de_fb_uploads/ directory and achieve Remote Code Execution by accessing the uploaded file via HTTP. The vulnerability was partially patched in version 5.1.3.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

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

## Is CVE-2026-5524 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-5524 exists.

Public exploit code:

- https://github.com/iicaicai/CVE-2026-5524-PoC (github_poc): https://github.com/iicaicai/CVE-2026-5524-PoC
- Divi Form Builder <=5.1.8 - Unauthenticated Arbitrary File Upload RCE (nuclei): http/cves/2026/CVE-2026-5524.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2026-5524 is a critical vulnerability in Divi Form Builder, published on 2 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-5524 exists.

Affected product: Divi Form Builder. 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-5524/ (Markdown: https://insights.sbomify.com/CVE-2026-5524/index.md)
```

## Sources

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

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