Skip to content

CVE-2026-5524

Unrestricted Upload of Dangerous File Type: Is CVE-2026-5524 real, exploitable, or a false positive? Here's the community verdict.

☆ Watch

signals

public sources

Exploited in wild
Not listed
CISA KEV
Public exploit
PoC (unverified)
Metasploit/EDB/PoC
Base severity
9.8 Critical
CVSS
Exploitation prob.
0.5%
FIRST EPSS
Weakness
CWE-434 · Unrestricted Upload of Dangerous File Type
CWE

High CVSS base score, but low real-world exploitation probability (EPSS). Likely less urgent than the score implies.

public exploits

links to sources — we don’t host code
GitHub PoCunverified

Unverified proof-of-concept code has been published. It may or may not be functional — assess before relying on it.

baseline read

auto · not a community verdict

Real, but low real-world risk

A genuine vulnerability on paper, but EPSS shows little real-world exploitation — the base score may overstate urgency. This is not the same as a false positive.

Based on CVSS · FIRST EPSS

Confirm or dispute →

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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.

References

NVD MITRE CVE.org

Published

Embed this verdict
TruePositive verdict for CVE-2026-5524
Markdown
[![TruePositive verdict](https://www.truepositive.app/cve/CVE-2026-5524/badge.svg)](https://www.truepositive.app/cve/CVE-2026-5524)
HTML
<a href="https://www.truepositive.app/cve/CVE-2026-5524"><img src="https://www.truepositive.app/cve/CVE-2026-5524/badge.svg" alt="TruePositive verdict for CVE-2026-5524"></a>

Live badge that updates automatically as the community verdict changes.

Community ground truth

Be the first practitioner to weigh in

So far this is only TruePositive's editorial baseline from public sources. Add your real-world verdict below — it becomes the signal the next person triaging this relies on.

🥇 The first 50 practitioners to contribute earn a Founding Contributor badge.

In your experience, is this finding real and exploitable?

awaiting field verdicts
Real, but not a risk here
Not a real issue

Curated baseline: A curated baseline from public sources, shown separately from community verdicts.

No account needed. Anonymous verdicts post as an unverified signal. Log in to make yours verified and earn reputation.

Field notes & remediation

Verdicts are the quick signal. Notes are the evidence and fixes behind them.

  • 0
    Field note · TruePositive EditorialCurated

    Proof-of-concept code is on GitHub. Exploitation has been demonstrated, though it may need adapting to a real target. It is reachable over the network with no authentication and no user interaction, which is the most dangerous profile. Not an emergency for most teams, but patch it in your normal cycle and check whether the affected component is actually exposed in your setup.

Add a field note or remediationoptional
Note type

What are you adding?

Markdown supported · minimum 20 characters.

Related CVEs

Same weakness: CWE-434 · Unrestricted Upload of Dangerous File Type.