# CVE-2026-4548: mickasmt next-saas-stripe-starter update-user-role.ts updateUserrole improper authorization

> Attackers can improperly modify user roles via the update-user-role function, leading to privilege escalation in the Next.js SaaS starter application.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **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:** 22 Mar 2026
- **Updated:** 23 Mar 2026
- **Also known as:** GHSA-8fh2-hm78-4frg

## What is CVE-2026-4548?

CVE-2026-4548 is a medium-severity missing authorization vulnerability in mickasmt next-saas-stripe-starter, published on 22 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was detected in mickasmt next-saas-stripe-starter 1.0.0. Affected by this vulnerability is the function updateUserrole of the file actions/update-user-role.ts. The manipulation of the argument userId/role results in improper authorization. The attack may be launched remotely.

Weakness: CWE-285 (Improper Authorization), CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2026-4548 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-4548 is a medium-severity missing authorization vulnerability in mickasmt next-saas-stripe-starter, published on 22 Mar 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-4548 exists.

Affected product: mickasmt next-saas-stripe-starter. 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-4548/ (Markdown: https://insights.sbomify.com/CVE-2026-4548/index.md)
```

## Sources

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

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