{"vuln_id":"GHSA-c7hf-c5p5-5g6h","aliases":["CVE-2026-32230"],"description":"Missing Authorization Check on Ping Badge Endpoint Leaks Ping times of montors without needing to be on a status page","published_at":"2026-03-11T06:52:49Z","modified_at":"2026-03-11T15:06:53Z","first_seen_at":"2026-11-22T13:40:14.914220Z","severity":"medium","severity_source":"ghsa","cvss_score":5.3,"cvss_vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","cwe":["CWE-862"],"vendor":null,"product":null,"kev":{"is_kev":false,"date_added":null,"due_date":null,"ransomware":false},"epss":null,"epss_percentile":null,"nvd_status":null,"enriched_at":null,"links":{"nvd":"https://github.com/advisories/GHSA-c7hf-c5p5-5g6h"},"matched_alias":null,"items":[{"id":12012,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"GHSA-c7hf-c5p5-5g6h / CVE-2026-32230: Missing Authorization Check on Ping Badge Endpoint Leaks Ping times of montors without needing to be on a status page","summary":"Missing Authorization Check on Ping Badge Endpoint Leaks Ping times of montors without needing to be on a status page ## Summary The `GET /api/badge/:id/ping/:duration?` endpoint in `server/routers/api-router.js` does not verify that the requested monitor belongs to a public group. All other badge endpoints check `AND public = 1` in their SQL query before returning data. The ping endpoint skips this check entirely, allowing unauthenticated users to extract average ping/response time data for private monitors. ## Affected Code File: `server/routers/api-router.js`, approximately line 304 The ping badge endpoint directly calls `UptimeCalculator.getUptimeCalculator(requestedMonitorId)` without first checking if the monitor is public. Compare with the status badge endpoint (~line 148) which correctly queries: ```sql SELECT monitor_group.monitor_id FROM monitor_group, `group` WHERE monitor_group.group_id = `group`.id AND monitor_group.monitor_id = ? AND public = 1 ``` ## Protected vs Vulnerable Endpoints | Endpoint | Has public=1 check? | |----------|-------------------| | /api/badge/:id/status | Yes | | /api/badge/:id/uptime/:duration? | Yes | | /api/badge/:id/avg-response/:duration? | Yes | | /api/badge/:id/cert-exp | Yes | | /api/badge/:id/response | Yes | | /api/badge/:id/ping/:duration? | **No — vulnerable** | ## PoC 1. Install Uptime Kuma (tested on latest v2 stable via Docker) 2. Create an HTTP(s) monitor (e.g., monitoring http://localhost:3001) 3. Do NOT add the monitor to any public status page or group 4. Wait for heartbeats to accumulate (~5 minutes) 5. Query unauthenticated: ```bash curl http://localhost:3001/api/badge/1/status → returns N/A (correct, monitor is private) curl http://localhost:3001/api/badge/1/ping/24 → returns \"Avg. Ping (24h): 10ms\" (LEAKED) ``` ## Impact An unauthenticated attacker can: - Enumerate private monitor IDs - Extract average response time data for private monitors - Infer existence and reachability of internal monitored services ## Suggested Fix Add the same public monitor check before the UptimeCalculator call: ```javascript let publicMonitor = await R.getRow(` SELECT monitor_group.monitor_id FROM monitor_group, \\`group\\` WHERE monitor_group.group_id = \\`group\\`.id AND monitor_group.monitor_id = ? AND public = 1 `, [requestedMonitorId]); if (!publicMonitor) { badgeValues.message = \"N/A\"; badgeValues.color = badgeConstants.naColor; } ``` Affected packages: npm:uptime-kuma Patched: uptime-kuma 2.2.0","url":"https://github.com/louislam/uptime-kuma/security/advisories/GHSA-c7hf-c5p5-5g6h","published_at":"2026-03-11T06:52:49Z","updated_at":"2026-03-11T15:06:53Z","fetched_at":"2026-11-22T13:40:14.883733Z","severity":"medium","cvss_score":5.3,"epss":0.00981,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":"CVE-2026-32230","vuln_ids":["CVE-2026-32230","GHSA-C7HF-C5P5-5G6H"],"tags":["repo-advisory","npm","CWE-862","security","repo:louislam/uptime-kuma"],"cluster_id":11316,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12012","html":"https://vulnwatch.ve1ve2.com/item/12012"}},{"id":12697,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"[SECURITY RELEASE] louislam/uptime-kuma 2.2.0","summary":"Fixes advisories: GHSA-c7hf-c5p5-5g6h\n\nSecurity keywords: security, GHSA-C7HF-C5P5-5G6H\n\n### 🆕 New Features\r\n- #7088 feat(proxy): allow socks proxy for the notifications (Thanks @ASLanin)\r\n- #7046 feat: add whatsApp (360messenger) notification provider (Thanks @WaMessenger)\r\n- #6989 feat: allow templating in the Signal notificaiton provider (Thanks @karthikeya-333)\r\n\r\n### 💇‍♀️ Improvements\r\n- #6979 refactor: improve SQLite multiple connections \r\n\r\n### 🐞 Bug Fixes\r\n- #7019 fix: Uptime Kuma is not able to start on older version of Node.js 20 (~20.17.0) \r\n- #7076 fix(monitor-list): cannot display monitor name in full width \r\n- #7069 fix(monitor-list): tag list do not update \r\n- #7056 fix(globalping): retry creating the measurement on status 500 (Thanks @radulucut)\r\n- #7055 fix(globalping): show error message when using multiple locations (Thanks @radulucut)\r\n- #7048 fix: Fix domain validation not allowing for PTR DNS records (Thanks @sgdc3)\r\n- #7045 fix: Remove forced DOWN status in group monitor (Thanks @MayMeow)\r\n- #7043 fix: Setting Status Page Analytics Type to \"None\" fails with SQLite constraint violation \r\n- #7011 fix(edit-monitor): several issues in edit page \r\n- #7010 fix(edit-monitor): url validation is incorrect \r\n- #6999 fix: show actual bind address in startup logs (Thanks @mixelburg)\r\n- #6994 fix: preserve Domain Name Expiry Notification setting when editing monitor (Thanks @RohitDarekar816)\r\n- #6984 fix: show certificate expiry on status page for TCP monitors (Thanks @mixelburg)\r\n\r\n### ⬆️ Security Fixes\r\n- GHSA-c7hf-c5p5-5g6h Missing Authorization Check on Ping Badge Endpoint Leaks Ping times of montors (Thanks @kuranikaran)\r\n\r\n### 🦎 Translation Contributions\r\n- #7072 #7007 chore: Translations Update from Weblate (Thanks @2000Arion @abcsnoob @aindriu80 @Aluisio @AnnAngela @AntonPalmqvist @BelenCaSa @cyril59310 @dodog @florian-berger @helakostain @ivanbratovic @kiznick @LovesAsuna @mariogarridopt @MrDariusz @MrEddX @robertcoroianu @Virenbar)\r\n\r\n### Others\r\n\r\n- #7015 chore: follow up #7013 \r\n- #7013 chore: add PR description template check workflow \r\n- #5179 feat: structured logging (JSON) (Thanks @SapphicCode)\r\n- #7092 chore: update to 2.2.0 \r\n- #7071 #6991 chore: Update dependencies \r\n- #7032 chore: remove @aws-sdk, @azure packages \r\n- #7077 chore: generate package-lock.json from scratch to ensure accuracy \r\n- #7058 chore: improve changelog generator ","url":"https://github.com/louislam/uptime-kuma/releases/tag/2.2.0","published_at":"2026-03-05T02:08:14Z","updated_at":null,"fetched_at":"2026-11-22T14:05:37.744918Z","severity":"medium","cvss_score":5.3,"epss":0.00981,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":"CVE-2026-32230","vuln_ids":["CVE-2026-32230","GHSA-C7HF-C5P5-5G6H"],"tags":["release","repo:louislam/uptime-kuma","security","stack","uptime-kuma"],"cluster_id":11316,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12697","html":"https://vulnwatch.ve1ve2.com/item/12697"}}]}