/

CVE-2026-58054

Severity:

HIGH RISK

(7.2)

Privilege Misconfiguration (CWE-269) in MyBB ACP Users

CVE-2026-58054

Deferred

Vulnerability type

Category:

Privilege Management Misconfiguration

CWE:

CWE-269

Impact:

Privilege Escalation to Full Administrator

Severity:

HIGH RISK

(7.2)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

MyBB 1.8.40 contains a privilege misconfiguration in the Admin Control Panel user management module that allows limited administrators to assign the full Administrators group to any account.

When a delegated admin can manage users, they may leverage this flaw to escalate their own or another account's privileges to full Administrator, becoming critical in environments with granular ACP role delegation.

MyBB 1.8.40 contains a privilege misconfiguration in the Admin Control Panel user management module that allows limited administrators to assign the full Administrators group to any account.

When a delegated admin can manage users, they may leverage this flaw to escalate their own or another account's privileges to full Administrator, becoming critical in environments with granular ACP role delegation.

Affected context

This vulnerability appears in MyBB installations that use the Admin Control Panel (ACP) with delegated or limited admin accounts.

It is relevant in deployments where:

  • Certain ACP users are granted only user-management permissions
  • Group-level permissions are expected to enforce stricter access boundaries
  • The Administrators group (gid 4) is treated as a highly privileged role

In such setups, the user management interface exposes high-privilege groups without additional checks, weakening the intended separation of duties.

This vulnerability appears in MyBB installations that use the Admin Control Panel (ACP) with delegated or limited admin accounts.

It is relevant in deployments where:

  • Certain ACP users are granted only user-management permissions
  • Group-level permissions are expected to enforce stricter access boundaries
  • The Administrators group (gid 4) is treated as a highly privileged role

In such setups, the user management interface exposes high-privilege groups without additional checks, weakening the intended separation of duties.

Exploit preconditions

  • Attack surface: Admin Control Panel (user management module)
  • Required access: An authenticated ACP account with permission to create or edit users (delegated user-management rights)
  • Trigger point: Using the ACP user editor to assign a user to the Administrators group (gid 4)
  • Why exploitation is possible: The user module presents the Administrators group as a selectable option, and the datahandler's verify_usergroup() function unconditionally approves the assignment instead of enforcing permission-aware constraints.
  • Attack surface: Admin Control Panel (user management module)
  • Required access: An authenticated ACP account with permission to create or edit users (delegated user-management rights)
  • Trigger point: Using the ACP user editor to assign a user to the Administrators group (gid 4)
  • Why exploitation is possible: The user module presents the Administrators group as a selectable option, and the datahandler's verify_usergroup() function unconditionally approves the assignment instead of enforcing permission-aware constraints.

Why this happens

The bug stems from insufficient authorization checks around group assignment within the ACP's user management workflow.

While MyBB supports delegated admin permissions, the logic that validates which groups a limited admin may assign does not enforce any restriction on high-privilege roles.

This corresponds to CWE-269: Improper Privilege Management, where the system fails to uphold intended privilege boundaries, allowing a lower-privileged administrator to directly grant full administrative rights via group membership configuration.

The bug stems from insufficient authorization checks around group assignment within the ACP's user management workflow.

While MyBB supports delegated admin permissions, the logic that validates which groups a limited admin may assign does not enforce any restriction on high-privilege roles.

This corresponds to CWE-269: Improper Privilege Management, where the system fails to uphold intended privilege boundaries, allowing a lower-privileged administrator to directly grant full administrative rights via group membership configuration.

Potential impact

  • A limited ACP user may escalate their own account to full Administrator privileges.
  • Delegated admins could grant full Administrator access to other accounts.
  • Complete control over forum configuration, user accounts, and permissions can be obtained.
  • Access to sensitive data, logs, and moderation tools may be expanded.
  • Ability to install plugins, modify themes, and alter security-related settings could be gained.
  • A limited ACP user may escalate their own account to full Administrator privileges.
  • Delegated admins could grant full Administrator access to other accounts.
  • Complete control over forum configuration, user accounts, and permissions can be obtained.
  • Access to sensitive data, logs, and moderation tools may be expanded.
  • Ability to install plugins, modify themes, and alter security-related settings could be gained.

General mitigation guidance

Effective mitigation focuses on enforcing strong privilege boundaries in role and group assignment logic.

Helpful patterns include:

  • Introducing explicit authorization checks before allowing group changes, especially for highly privileged groups such as Administrators.
  • Separating user-management duties from permission- and group-management duties, ensuring that only fully trusted admins can assign or modify privileged groups.
  • Implementing policy-based constraints (e.g., deny-list or allow-list of groups) for delegated admins to prevent inadvertent privilege escalation.
  • Reducing the set of ACP accounts with access to sensitive role-management operations and reviewing delegation configurations regularly.
  • Adopting "secure-by-default" UI behavior that hides or disables high-privilege groups when the current admin lacks the necessary permission tier.

Effective mitigation focuses on enforcing strong privilege boundaries in role and group assignment logic.

Helpful patterns include:

  • Introducing explicit authorization checks before allowing group changes, especially for highly privileged groups such as Administrators.
  • Separating user-management duties from permission- and group-management duties, ensuring that only fully trusted admins can assign or modify privileged groups.
  • Implementing policy-based constraints (e.g., deny-list or allow-list of groups) for delegated admins to prevent inadvertent privilege escalation.
  • Reducing the set of ACP accounts with access to sensitive role-management operations and reviewing delegation configurations regularly.
  • Adopting "secure-by-default" UI behavior that hides or disables high-privilege groups when the current admin lacks the necessary permission tier.

How teams detect issues like this

Organizations can detect and monitor this type of misconfiguration-driven escalation through:

  • Reviewing ACP authorization logic for group and role assignment paths, focusing on checks around privileged groups.
  • Employing code review practices that flag any user or group management operations lacking permission-aware validation.
  • Using static analysis or security linters to highlight areas where privilege levels are modified without corresponding access checks.
  • Monitoring audit logs for suspicious changes in group memberships, particularly assignments into the Administrators group from non-full-admin accounts.
  • Enforcing configuration and policy audits that validate delegated admin capabilities against documented security expectations.

Organizations can detect and monitor this type of misconfiguration-driven escalation through:

  • Reviewing ACP authorization logic for group and role assignment paths, focusing on checks around privileged groups.
  • Employing code review practices that flag any user or group management operations lacking permission-aware validation.
  • Using static analysis or security linters to highlight areas where privilege levels are modified without corresponding access checks.
  • Monitoring audit logs for suspicious changes in group memberships, particularly assignments into the Administrators group from non-full-admin accounts.
  • Enforcing configuration and policy audits that validate delegated admin capabilities against documented security expectations.

Sources

SourceLink
github.comgithub.com/bikini/exploitarium/tree/main/mybb-limited-acp-to-admin
vulncheck.comvulncheck.com/advisories/mybb-privilege-escalation-from-limited-acp-user-management-to-administrator

Frequently asked

questions

No. Exploitation requires access to the Admin Control Panel with user-management permissions. Regular users without ACP access cannot directly exploit this flaw.

An attacker must control an ACP account that can create or edit users. With that delegated capability, they can assign the Administrators group to themselves or another account.

The safest pattern is to implement strict authorization checks around any operation that modifies roles, groups, or privilege levels, ensuring that only appropriately privileged administrators can assign high-privilege groups.

Preventive strategies include designing clear separation of duties for admin roles, enforcing permission-aware validation on all group and role changes, conducting security-focused code reviews on authorization logic, and regularly auditing ACP accounts and their delegated permissions.

No. Exploitation requires access to the Admin Control Panel with user-management permissions. Regular users without ACP access cannot directly exploit this flaw.

An attacker must control an ACP account that can create or edit users. With that delegated capability, they can assign the Administrators group to themselves or another account.

The safest pattern is to implement strict authorization checks around any operation that modifies roles, groups, or privilege levels, ensuring that only appropriately privileged administrators can assign high-privilege groups.

Preventive strategies include designing clear separation of duties for admin roles, enforcing permission-aware validation on all group and role changes, conducting security-focused code reviews on authorization logic, and regularly auditing ACP accounts and their delegated permissions.

Find out what's already
exploitable in your codebase.