# CVE-2026-79411: Privilege escalation in n/a

> Authenticated users with limited edit permissions can escalate to full administrator by modifying their own role, exposing sensitive data and configurations.

- **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:** 15 Sep 2026
- **Updated:** 16 Sep 2026
- **Also known as:** GHSA-qx3f-h864-653p

## What is CVE-2026-79411?

CVE-2026-79411 is a high-severity vulnerability in n/a, published on 15 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Incorrect privilege assignment in the admin user-management component of Webkul Bagisto 2.4.9 allows an authenticated backend user holding only the settings.users.edit permission to escalate to full administrator. The user-update endpoint (route admin.settings.users.update, UserController::update()) does not verify that the actor is permitted to grant the requested role, does not prevent a user from changing their own role, and does not restrict assignment to roles whose permission set is a subset of the actor's own. By submitting a request that sets role_id to the Administrator role for their own account, a low-privileged administrator gains every admin-panel capability, including store configuration, payment gateway credentials, and customer PII.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-79411 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-79411 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-79411 is a high-severity vulnerability in n/a, published on 15 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-79411 exists.

Affected product: n/a. 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-79411/ (Markdown: https://insights.sbomify.com/CVE-2026-79411/index.md)
```

## Sources

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

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