# CVE-2026-5523: Missing authorization in Divi Form Builder

> Authenticated subscribers can escalate privileges and take over administrator accounts by modifying user profiles without proper authorization checks.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jul 2026
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-c9hw-vrgh-hh3m

## What is CVE-2026-5523?

CVE-2026-5523 is a high-severity missing authorization vulnerability in Divi Form Builder, published on 9 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Divi Form Builder plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 5.1.8. This is due to the update_user() function accepting a user ID parameter from form submissions without verifying that the authenticated user has permission to edit that specific user account, and the handle_register_submission() function only checking if any user is logged in rather than validating permissions for the target user. This makes it possible for authenticated attackers, with subscriber-level access and above, to change the email address and password of any user account, including administrators, resulting in complete account takeover.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-5523 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-5523 is a high-severity missing authorization vulnerability in Divi Form Builder, published on 9 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-5523 in the wild and no public exploit code.

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-5523/ (Markdown: https://insights.sbomify.com/CVE-2026-5523/index.md)
```

## Sources

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

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