CVE-2025-66028

CVE-2025-66028 is a medium-severity incorrect authorization vulnerability in @oneuptime/common (npm), affecting versions < 8.0.5567. It is fixed in 8.0.5567.

Summary

During the login process, the server response included a parameter called isMasterAdmin. By intercepting and modifying this parameter value from false to true, a user is able to gain access to the admin dashboard interface. However, despite accessing the admin panel, the user does not have sufficient permissions to view or interact with actual data.

PoC

Intercept the login response and change "isMasterAdmin": false → "isMasterAdmin": true

Impact

The admin dashboard is viewable.

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

Affected versions

@oneuptime/common (< 8.0.5567)

Security releases

@oneuptime/common → 8.0.5567 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

Upgrade @oneuptime/common to 8.0.5567 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is CVE-2025-66028? CVE-2025-66028 is a medium-severity incorrect authorization vulnerability in @oneuptime/common (npm), affecting versions < 8.0.5567. It is fixed in 8.0.5567. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
  2. Which versions of @oneuptime/common are affected by CVE-2025-66028? @oneuptime/common (npm) versions < 8.0.5567 is affected.
  3. Is there a fix for CVE-2025-66028? Yes. CVE-2025-66028 is fixed in 8.0.5567. Upgrade to this version or later.
  4. Is CVE-2025-66028 exploitable, and should I be worried? Whether CVE-2025-66028 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  5. What actually determines whether CVE-2025-66028 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  6. How do I fix CVE-2025-66028? Upgrade @oneuptime/common to 8.0.5567 or later.

Other vulnerabilities in @oneuptime/common

CVE-2026-30959CVE-2026-30957CVE-2026-30956CVE-2026-30920CVE-2026-30921

Stop the waste.
Protect your environment with Kodem.