CVE-2023-44400 Uptime Kuma has Persistentent User Sessions
Attackers with device access can maintain persistent account access in Uptime Kuma due to missing session token verification after password changes or inactivity.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2023-44400?
CVE-2023-44400 is a medium-severity vulnerability in louislam uptime-kuma, published on 9 Oct 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
Uptime Kuma is a self-hosted monitoring tool. Prior to version 1.23.3, attackers with access to a user's device can gain persistent account access. This is caused by missing verification of Session Tokens after password changes and/or elapsed inactivity periods. Version 1.23.3 has a patch for the issue.
Weakness: CWE-384
Which versions are affected by CVE-2023-44400?
2 open source packages ship an affected version, including uptime-kuma. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
uptime-kuma npm | All versions | 1.23.3 |
uptime-kuma npm | All versions | 1.23.3 |
Products include Uptime.kuma Uptime Kuma.
How do I fix CVE-2023-44400?
Upgrade uptime-kuma to 1.23.3 or later.
Is CVE-2023-44400 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-44400 exists.
Other vulnerabilities in louislam uptime-kuma
- CVE-2026-33130 Uptime Kuma: SSTI in Notification Templates Allows Arbitrary File Read (Incomplete Fix for GHSA-vffh-c9pq-4crh)
- CVE-2023-49276 Attribute Injection leading to XSS(Cross-Site-Scripting) in uptime-kuma
- CVE-2026-32230 Uptime Kuma is Missing Authorization Checks on Ping Badge Endpoint, Leaks Ping times of monitors without needing to be on a status page
Sources
Also known as GHSA-g9v2-wqcj-j99g.