How severe is GHSA-675q-66gf-gqg8?

No CVSS score has been assigned to GHSA-675q-66gf-gqg8 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-675q-66gf-gqg8?

GHSA-675q-66gf-gqg8 affects the following packages: @oneuptime/common (npm). Ecosystems affected: npm.

How do I fix GHSA-675q-66gf-gqg8?

Update @oneuptime/common to 8.0.5567 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-675q-66gf-gqg8 is resolved across your whole dependency graph.

How do I detect GHSA-675q-66gf-gqg8 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @oneuptime/common, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-675q-66gf-gqg8 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-675q-66gf-gqg8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-675q-66gf-gqg8 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-675q-66gf-gqg8?

GHSA-675q-66gf-gqg8 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 25th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-675q-66gf-gqg8?

GHSA-675q-66gf-gqg8 is classified as CWE-284 (CWE-284). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-675q-66gf-gqg8 published, and has it been updated?

GHSA-675q-66gf-gqg8 was published on November 25, 2025 and was last updated on November 27, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

OneUptime is Vulnerable to Privilege Escalation via Login Response ManipulationGHSA-675q-66gf-gqg8

Fix: OneUptime/oneuptime@3e72b2a

GHSA-675q-66gf-gqg8 is a CWE-284 vulnerability in @oneuptime/common. A fix is available for @oneuptime/common — see the affected versions and patch details below.

Also known asCVE-2025-66028

Published

Nov 25, 2025

Updated

Nov 27, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA’s SSVC triage for GHSA-675q-66gf-gqg8.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs25th percentile — riskier than 25% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@oneuptime/commonnpm

20Kdownloads / week

Description

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 <img width="1405" height="567" alt="image" src="https://github.com/user-attachments/assets/7036398b-bb41-46c1-b66a-e49ec2bc3abb" /> <img width="1533" height="476" alt="2" src="https://github.com/user-attachments/assets/4efcaef5-a939-4729-be43-3af62a7d02f8" />

Impact

The admin dashboard is viewable.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@oneuptime/common`	all versions	8.0.5567`npm install @oneuptime/common@8.0.5567`

Affected Products

1 product · 1 configurations

Application

oneuptimehackerbay

< 8.0.5567

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @oneuptime/common, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @oneuptime/common to 8.0.5567 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-675q-66gf-gqg8 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### 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 <img width="1405" height="567" alt="image" src="https://github.com/user-attachments/assets/7036398b-bb41-46c1-b66a-e49ec2bc3abb" /> <im

O3 Security · Impact-Aware SCA

Is GHSA-675q-66gf-gqg8 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works