CVE-2023-49805

HIGHNVD 8.86.0
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.0 under NVD CVSS v3. EPSS exploit probability: 0.0%, top 98% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Uptime Kuma is an easy-to-use self-hosted monitoring tool. Prior to version 1.23.9, the application uses WebSocket (with Socket.io), but it does not verify that the source of communication is valid. This allows third-party website to access the application on behalf of their client. When connecting to the server using Socket.IO, the server does not validate the Origin header leading to other site being able to open connections to the server and communicate with it. Other websites still need to authenticate to access most features, however this can be used to circumvent firewall protections made in place by people deploying the application.

Without origin validation, Javascript executed from another origin would be allowed to connect to the application without any user interaction. Without login credentials, such a connection is unable to access protected endpoints containing sensitive data of the application. However, such a connection may allow attacker to further exploit unseen vulnerabilities of the application. Users with "No-auth" mode configured who are relying on a reverse proxy or firewall to provide protection to the application would be especially vulnerable as it would grant the attacker full access to the application.

In version 1.23.9, additional verification of the HTTP Origin header has been added to the socket.io connection handler. By default, if the Origin header is present, it would be checked against the Host header. Connection would be denied if the hostnames do not match, which would indicate that the request is cross-origin. Connection would be allowed if the Origin header is not present. Users can override this behavior by setting environment variable UPTIME_KUMA_WS_ORIGIN_CHECK=bypass.

CVSS v3
8.8
EG Score
6.0(medium)
EPSS
29.7%
KEV
Not listed

Published

December 11, 2023

Last Modified

June 17, 2026

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 45× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 08:26 UTCEPSS rescore
  2. 2026-07-09 19:08 UTCEPSS rescore
  3. 2026-07-08 15:13 UTCEPSS rescore
  4. 2026-07-07 13:44 UTCEPSS rescore
  5. 2026-07-07 13:44 UTCEPSS rescore
  6. 2026-07-06 16:26 UTCEPSS rescore
  7. 2026-07-06 16:26 UTCEPSS rescore
  8. 2026-07-06 02:22 UTCEPSS rescore
  9. 2026-07-05 02:29 UTCEPSS rescore
  10. 2026-07-04 06:29 UTCEPSS rescore
  11. 2026-07-04 06:29 UTCEPSS rescore
  12. 2026-07-02 16:59 UTCEPSS rescore
  13. 2026-07-01 15:05 UTCEPSS rescore
  14. 2026-06-30 23:21 UTCEPSS rescore
  15. 2026-06-30 23:21 UTCEPSS rescore
  16. 2026-06-28 14:06 UTCEPSS rescore
  17. 2026-06-28 14:06 UTCEPSS rescore
  18. 2026-06-28 04:55 UTCEPSS rescore
  19. 2026-06-27 03:07 UTCEPSS rescore
  20. 2026-06-27 02:37 UTCOSV refresh
  21. 2026-06-25 13:48 UTCEPSS rescore
  22. 2026-06-25 13:48 UTCEPSS rescore
  23. 2026-06-24 14:04 UTCEPSS rescore
  24. 2026-06-24 14:04 UTCEPSS rescore
  25. 2026-06-24 06:33 UTCNVD updateCVSS v3 → 8.8 · severity → HIGH
Show 56 more
  1. 2026-06-23 21:31 UTCEPSS rescore
  2. 2026-06-23 21:31 UTCEPSS rescore
  3. 2026-06-22 14:24 UTCEPSS rescore
  4. 2026-06-22 14:24 UTCEPSS rescore
  5. 2026-06-21 14:55 UTCEPSS rescore
  6. 2026-06-21 14:55 UTCEPSS rescore
  7. 2026-06-21 01:58 UTCEPSS rescore
  8. 2026-06-21 01:58 UTCEPSS rescore
  9. 2026-06-19 19:24 UTCEPSS rescore
  10. 2026-06-19 19:24 UTCEPSS rescore
  11. 2026-06-18 17:51 UTCEPSS rescore
  12. 2026-06-17 17:51 UTCEPSS rescore
  13. 2026-06-16 17:51 UTCEPSS rescore
  14. 2026-06-16 17:51 UTCEPSS rescore
  15. 2026-06-15 17:47 UTCEPSS rescore
  16. 2026-06-14 23:16 UTCEPSS rescore
  17. 2026-06-13 22:59 UTCEPSS rescore
  18. 2026-06-13 22:59 UTCEPSS rescore
  19. 2026-06-12 23:11 UTCEPSS rescore
  20. 2026-06-12 23:10 UTCEPSS rescore
  21. 2026-06-11 13:59 UTCEPSS rescore
  22. 2026-06-10 22:17 UTCEPSS rescore
  23. 2026-06-10 13:21 UTCEPSS rescore
  24. 2026-06-09 12:49 UTCOSV refresh
  25. 2026-06-08 14:16 UTCEPSS rescore
  26. 2026-06-08 14:16 UTCEPSS rescore
  27. 2026-06-07 15:24 UTCEPSS rescore
  28. 2026-06-07 15:23 UTCEPSS rescore
  29. 2026-06-06 13:46 UTCEPSS rescore
  30. 2026-06-06 13:46 UTCEPSS rescore
  31. 2026-06-05 22:46 UTCEPSS rescore
  32. 2026-06-05 22:46 UTCEPSS rescore
  33. 2026-06-05 06:09 UTCEPSS rescore
  34. 2026-06-05 06:09 UTCEPSS rescore
  35. 2026-06-05 06:09 UTCEPSS rescore
  36. 2026-06-04 13:11 UTCEPSS rescore
  37. 2026-06-04 13:11 UTCEPSS rescore
  38. 2026-06-04 13:11 UTCEPSS rescore
  39. 2026-06-02 20:12 UTCEPSS rescore
  40. 2026-06-02 20:12 UTCEPSS rescore
  41. 2026-06-01 13:51 UTCEPSS rescore
  42. 2026-06-01 13:51 UTCEPSS rescore
  43. 2026-05-31 22:30 UTCEPSS rescore
  44. 2026-05-31 22:30 UTCEPSS rescore
  45. 2026-05-31 00:15 UTCEPSS rescore
  46. 2026-05-31 00:15 UTCEPSS rescore
  47. 2026-05-29 13:43 UTCEPSS rescore
  48. 2026-05-28 13:44 UTCEPSS rescore
  49. 2026-05-27 13:39 UTCEPSS rescore
  50. 2026-05-27 13:39 UTCEPSS rescore
  51. 2026-05-26 13:43 UTCEPSS rescore
  52. 2026-05-26 13:43 UTCEPSS rescore
  53. 2026-05-26 07:18 UTCEPSS rescore
  54. 2026-05-26 07:18 UTCEPSS rescore
  55. 2026-05-26 07:18 UTCEPSS rescore
  56. 2026-05-24 12:25 UTCEG score recompute

Frequently asked(5)

What is CVE-2023-49805?
CVE-2023-49805 is a high vulnerability published on December 11, 2023. Uptime Kuma is an easy-to-use self-hosted monitoring tool. Prior to version 1.23.9, the application uses WebSocket (with Socket.io), but it does not verify that the source of communication is valid. This allows third-party website to access the application on behalf of their client. When connecting…
When was CVE-2023-49805 disclosed?
CVE-2023-49805 was first published in the National Vulnerability Database on December 11, 2023, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-49805 actively exploited?
CVE-2023-49805 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 29.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2023-49805?
CVE-2023-49805 has a CVSS v3 base score of 8.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 6.0.
How do I remediate CVE-2023-49805?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-49805, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2023-49805

Explore →

Is Your Infrastructure Affected by CVE-2023-49805?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.