Introduction

CVE-2026-5118 affects Divi Form Builder through version 5.1.2. The vulnerability allows unauthenticated attackers to create administrator accounts by manipulating the role value accepted during public form registration.

A public security-research repository documents the technical findings and proof-of-concept material associated with the issue. The discussion below focuses on the security impact, root cause, affected component, and defensive remediation rather than reproducing weaponized exploitation steps.

Vulnerability Overview

The vulnerable create_user functionality accepts a user-controlled role parameter without restricting it to the form's intended default role. A public registration form therefore becomes a potential privileged-account creation mechanism.

In simplified terms, the security problem looks like this:

Unauthenticated Form Submission
        │
        ▼
User Creation Function
        │
        ▼
User-controlled Role
        │
        ▼
Missing Role Allowlist
        │
        ▼
Administrator Account
        │
        ▼
Full WordPress Access

The important security principle is that untrusted client input must never be allowed to cross an authentication, authorization, filesystem, or code-execution boundary without strict server-side validation.

Why Is This Vulnerability Serious?

Allowing an unauthenticated user to choose the role of a newly created account directly breaks WordPress's authorization boundary.

The potential impact depends on the application's configuration, the privileges of the affected process, and whether vulnerable functionality is exposed to untrusted users.

Root Cause

The root cause is improper privilege management: role selection should be derived from trusted server-side configuration rather than public POST data.

A secure implementation should independently verify:

• Authentication and authorization requirements
• The ownership or scope of the requested object
• Input type, format, and allowed values
• Filesystem paths and canonical destinations where applicable
• File type and content where uploads are involved
• That privileged operations cannot be selected through client-controlled parameters
• That sensitive functionality fails closed when validation fails

Affected Versions / Components

The publicly documented affected details are:

These details are based on the public research repository and, where available, the corresponding NVD record. Administrators should verify the exact installed version and deployment configuration before determining exposure.

Public PoC

The associated repository contains research and proof-of-concept material demonstrating the vulnerability.

For defensive research, proof-of-concept code should only be used in an authorized laboratory environment or against systems for which explicit permission has been granted. Production systems should be tested using harmless validation methods whenever possible.

Security Impact

1. Administrator account creation

Administrator account creation can become a security concern depending on the deployment and the privileges of the affected component.

2. Privilege escalation

Privilege escalation can become a security concern depending on the deployment and the privileges of the affected component.

3. WordPress dashboard access

WordPress dashboard access can become a security concern depending on the deployment and the privileges of the affected component.

4. Website takeover

Website takeover can become a security concern depending on the deployment and the privileges of the affected component.

Detection and Mitigation

Administrators should first identify whether the affected component is installed and determine the exact version.

Recommended defensive actions include:

• Update to a fixed version when available.
• Disable public registration forms if not required.
• Enforce a server-side role allowlist.
• Review administrator accounts for unexpected additions.
• Monitor registration and form-submission logs.

Indicators of Compromise

For incident-response purposes, administrators should review application and web-server logs around the affected functionality.

A useful investigation should examine:

Application / Web Logs
        │
        ├── Unusual Requests to Vulnerable Functions
        ├── Unexpected Authentication Events
        ├── Suspicious File Operations
        ├── Unexpected Account / Role Changes
        ├── Recently Modified Files
        └── Unusual Outbound Connections

Log evidence should be correlated with account activity, filesystem changes, deployment history, and application configuration rather than treated as a single definitive indicator.

Conclusion

CVE-2026-5118 affects Divi Form Builder through version 5.1.2. The vulnerability allows unauthenticated attackers to create administrator accounts by manipulating the role value accepted during public form registration.

The main lesson is that security-sensitive functionality must enforce authorization and validation on the server side. Client-controlled identifiers, role values, filenames, MIME types, filesystem paths, and template content should never be trusted simply because they originated from an apparently legitimate application workflow.

For security researchers and developers, this issue provides a useful case study in secure application design, particularly around authorization boundaries, file handling, authentication, input validation, and defense-in-depth.

SOURCE: https://github.com/Yucaerin/CVE-2026-5118

References:

• https://nvd.nist.gov/vuln/detail/CVE-2026-5118