CVE-2026-5523 HIGH

CVE-2026-5523: Divi Form Builder <= 5.1.8 - Authenticated (Subscriber+) Missing Authorization to Privilege Escalation via User Profile Update Form

Vendor Divi Engine
Product Divi Form Builder
Weakness CWE-639 · IDOR
Published July 9, 2026
Last update July 9, 2026

CVSS base score

8.8/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality High
Integrity High

CVSS vector

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

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

Divi Form Builder versions 5.1.8 and earlier contain an authorization flaw that allows authenticated users with low privileges to read, modify, or delete sensitive data and disrupt site operations. The vulnerability requires a valid user account but no special interaction. Site administrators should update immediately to a version newer than 5.1.8.

What an attacker can do

03Attacker Capabilities

Read, modify, or delete sensitive data; disrupt site availability with a valid user account.

Potential impact on your site

04Site Impact

Any authenticated user can access or alter form data and settings, potentially exposing visitor submissions or breaking form functionality.

Conditions required to exploit

05Prerequisites

Attacker must have a low-privilege user account on the site; no user interaction required.

Key dates

06Disclosure timeline

July 9, 2026 CVE published
July 9, 2026 Record updated

Related vulnerabilities

08Related CVE