How severe is GHSA-23q2-5gf8-gjpp?

No CVSS score has been assigned to GHSA-23q2-5gf8-gjpp yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-23q2-5gf8-gjpp?

GHSA-23q2-5gf8-gjpp affects the following packages: uptime-kuma (npm). Ecosystems affected: npm.

How do I fix GHSA-23q2-5gf8-gjpp?

Update uptime-kuma to 1.23.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-23q2-5gf8-gjpp is resolved across your whole dependency graph.

How do I detect GHSA-23q2-5gf8-gjpp in my npm dependencies?

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

How do I mitigate GHSA-23q2-5gf8-gjpp if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-23q2-5gf8-gjpp?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-23q2-5gf8-gjpp can be triaged on real exposure rather than presence alone.

Is GHSA-23q2-5gf8-gjpp actively exploited in the wild?

No public exploit code has been indexed for GHSA-23q2-5gf8-gjpp 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.

When was GHSA-23q2-5gf8-gjpp published, and has it been updated?

GHSA-23q2-5gf8-gjpp was published on April 19, 2024. 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

GHSA-23q2-5gf8-gjpp — uptime-kuma

Fix: louislam/uptime-kuma@7a9e2f5

GHSA-23q2-5gf8-gjpp is a security vulnerability in uptime-kuma. A fix is available for uptime-kuma — see the affected versions and patch details below.

Enabling Authentication does not close all logged in socket connections immediately

Published

Apr 19, 2024

Updated

Apr 19, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Apr 19, 2024 · OSV.dev, 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

uptime-kumanpm

39downloads / week

Description

Summary

This is basically GHSA-88j4-pcx8-q4q but instead of changing passwords, when enabling authentication.

PoC

Open Uptime Kuma with authentication disabled
Enable authentication using another window
Access the platform using the previously logged-in window
Note that access (read-write) remains despite the enabled authentication
Expected behaviour:
- After enabling authentication, all previously connected sessions should be invalidated, requiring users to log in.
Actual behaviour:
- The system retains sessions and never logs out users unless explicitly done by clicking logout or refreshing the page.

Impact

See GHSA-g9v2-wqcj-j99g and GHSA-88j4-pcx8-q4q

TBH this is quite a niche edge case, so I don't know if this even warrants a security report.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`uptime-kuma`	all versions	1.23.12`npm install uptime-kuma@1.23.12`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for uptime-kuma, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update uptime-kuma to 1.23.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-23q2-5gf8-gjpp is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-23q2-5gf8-gjpp can be triaged on real exposure rather than presence alone.

Tailored to GHSA-23q2-5gf8-gjpp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary This is basically [GHSA-88j4-pcx8-q4q](https://github.com/louislam/uptime-kuma/security/advisories/GHSA-88j4-pcx8-q4q3) but instead of changing passwords, when enabling authentication. ### PoC - Open Uptime Kuma with authentication disabled - Enable authentication using another window - Access the platform using the previously logged-in window - Note that access (read-write) remains despite the enabled authentication - Expected behaviour: - After enabling authentication, all previously connected sessions should be invalidated, requiring users to log in. - Actual behaviour: - T

O3 Security · Impact-Aware SCA

Is GHSA-23q2-5gf8-gjpp in your dependencies?

O3 Security finds GHSA-23q2-5gf8-gjpp across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works