/

CVE-2026-79411

Severity:

HIGH RISK

(8.8)

Improper Privilege Management (CWE-269) in Bagisto

CVE-2026-79411

Deferred

Vulnerability type

Category:

Improper Privilege Management

CWE:

CWE-269

Impact:

Horizontal-to-vertical privilege escalation

Severity:

HIGH RISK

(8.8)

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

Webkul Bagisto contains an authorization flaw in its admin user-management component that allows an authenticated backend user with limited user-edit permission to assign themselves the full Administrator role. If the user can reach the affected update function, this may provide access to sensitive administrative functions and data.

Affected context

The issue occurs in Bagisto deployments where an authenticated backend user with the settings.users.edit permission can invoke the administrative user update flow. Risk is present when role changes are processed without checking whether the actor may grant the requested role, whether the target is the actor's own account, and whether the assigned role exceeds the actor's effective permissions.

Exploit preconditions

  • Attack surface: Authenticated administrative user-management functionality
  • Required access: A backend account holding the settings.users.edit permission
  • Trigger point: Processing of a user-update request that changes an account's role
  • Why exploitation is possible: The authorization logic does not adequately constrain self-role changes or prevent assignment of roles with greater privileges than those held by the actor

Why this happens

The underlying bug is an incomplete authorization check in the user-update operation. The application authorizes access to edit a user but does not separately authorize the security-sensitive action of granting a role, nor enforce a hierarchy or subset relationship between the actor's permissions and the requested role. This behavior maps to CWE-269, Improper Privilege Management, because a less-privileged principal can cause a higher-privilege identity to be assigned without an effective privilege boundary.

Potential impact

  • An attacker may gain full administrator capabilities in the backend
  • Store configuration and payment gateway credentials could be exposed or modified
  • Customer personally identifiable information could be accessed
  • Administrative accounts and application settings could be altered
  • The application could be used to facilitate broader compromise or data abuse

General mitigation guidance

Mitigation generally centers on treating role assignment as a privileged

security operation rather than as an ordinary user-edit action.

Common defensive patterns include:

  • Enforcing server-side authorization for every requested role transition
  • Preventing users from elevating their own role or privileges
  • Allowing assignment only to roles whose effective permissions are a subset of the actor's permissions
  • Separating user-profile editing from role and permission administration
  • Applying least privilege to administrative accounts and service identities
  • Requiring independent approval or stronger controls for highly privileged role changes
  • Using deny-by-default authorization and avoiding reliance on client-side restrictions

How teams detect issues like this

Detection approaches can include:

  • Static analysis and code review checks for role or permission updates that lack actor-versus-target authorization
  • Review of controller and policy paths handling role identifiers, especially where edit and grant permissions are conflated
  • Tests covering self-role changes, assignment of higher-privilege roles, and cross-scope role transitions
  • Audit-log monitoring for unexpected administrator-role assignments or privilege changes
  • Policy enforcement requiring explicit authorization checks for all role-management operations
  • Neutral automated code-review rules that flag user-controlled privilege fields without corresponding server-side validation

Sources

SourceLink
github.comgithub.com/isukasanuj/bagisto-cve/blob/main/CVE-2026-79411.md

Frequently asked

questions

An authenticated backend user may be able to exploit it if their account can access the affected user-update operation and holds the required user-edit permission.

No. The described condition requires an authenticated administrative or backend account; the exposure of that account and endpoint depends on deployment access controls.

Enforce server-side authorization for role assignment, block self-elevation, and require that any role granted is within the permissions the acting user is authorized to delegate.

Model role changes as privileged operations, test privilege-boundary transitions explicitly, use deny-by-default policies, and monitor audit logs for unexpected changes to high-privilege roles.

Find out what's already
exploitable in your codebase.