# CVE-2025-66028: OneUptime is Vulnerable to Privilege Escalation via Login Response Manipulation

> Attackers can escalate privileges to admin by manipulating the isMasterAdmin parameter in the login response, bypassing authorization checks.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Nov 2025
- **Updated:** 26 Nov 2025
- **Also known as:** GHSA-675q-66gf-gqg8

## What is CVE-2025-66028?

CVE-2025-66028 is a medium-severity vulnerability in oneuptime, published on 26 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OneUptime is a solution for monitoring and managing online services. Prior to version 8.0.5567, OneUptime is vulnerable to privilege escalation via Login Response Manipulation. During the login process, the server response included a parameter called isMasterAdmin. By intercepting and modifying this parameter value from false to true, it is possible to gain access to the admin dashboard interface. However, an attacker may be unable to view or interact with the data if they still do not have sufficient permissions. This issue has been patched in version 8.0.5567.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2025-66028?

2 open source packages ship an affected version, including @oneuptime/common. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@oneuptime/common` | npm | All versions | 8.0.5567 |
| `@oneuptime/common` | npm | All versions | 8.0.5567 |

Products: Hackerbay Oneuptime.

## How do I fix CVE-2025-66028?

Upgrade @oneuptime/common to 8.0.5567 or later.

## Is CVE-2025-66028 being exploited?

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

## Other vulnerabilities in oneuptime

- [CVE-2026-33396](https://insights.sbomify.com/CVE-2026-33396/): Code injection in oneuptime (critical 10.0)
- [CVE-2026-32306](https://insights.sbomify.com/CVE-2026-32306/): OneUptime ClickHouse SQL Injection via Aggregate Query Parameters (critical 10.0)
- [CVE-2026-30956](https://insights.sbomify.com/CVE-2026-30956/): OneUptime has authorization bypass via client‑controlled is-multi-tenant-query header (critical 10.0)
- [CVE-2026-30957](https://insights.sbomify.com/CVE-2026-30957/): OneUptime Synthetic Monitor RCE via exposed Playwright browser object (critical 10.0)
- [CVE-2026-30887](https://insights.sbomify.com/CVE-2026-30887/): OneUptime Affected by Unsandboxed Code Execution in Probe Allows Any Project Member to Achieve RCE (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-66028 and fix it if it is affected.

What it is: CVE-2025-66028 is a medium-severity vulnerability in oneuptime, published on 26 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-66028 exists.

Affected packages and fixed versions:
- @oneuptime/common (npm): affected all versions; fixed in 8.0.5567
- @oneuptime/common (npm): affected all versions; fixed in 8.0.5567

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-2025-66028/ (Markdown: https://insights.sbomify.com/CVE-2025-66028/index.md)
```

## Sources

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

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