{"vuln_id":"GHSA-9fg7-wgm7-57fh","aliases":[],"description":"RSS status feed does not set content type, leading to a Stored XSS in Public Status Page RSS Feed via CDATA escaped Monitor Name IF USING AN UNSECURE CLIENT","published_at":"2026-02-08T15:49:41Z","modified_at":"2026-02-08T15:49:41Z","first_seen_at":"2026-11-22T13:40:14.915208Z","severity":"low","severity_source":"ghsa","cvss_score":null,"cvss_vector":null,"cwe":["CWE-79"],"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-9fg7-wgm7-57fh"},"matched_alias":null,"items":[{"id":12013,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"GHSA-9fg7-wgm7-57fh: RSS status feed does not set content type, leading to a Stored XSS in Public Status Page RSS Feed via CDATA escaped Monitor Name IF USING AN UNSECURE CLIENT","summary":"RSS status feed does not set content type, leading to a Stored XSS in Public Status Page RSS Feed via CDATA escaped Monitor Name IF USING AN UNSECURE CLIENT\n\n### Summary\r\n\r\nThe RSS feed for public status pages returns a default `text/html` content type instead of a safe RSS/XML content type. Monitor names are already CDATA-escaped, so the content itself is safe. However, serving the feed as `text/html` can cause browsers to interpret it incorrectly, potentially exposing users to cross-site scripting if the feed is embedded in a web context.\r\n\r\n### Description\r\n\r\nMonitor names are stored safely and rendered within CDATA sections in RSS feed items. The feed is generated dynamically and returned using `response.send()`. Because no explicit content type is set, the response defaults to `text/html`.\r\n\r\nWhile the content is already escaped, serving it as HTML can cause browsers to parse the feed incorrectly, possibly leading to **script execution in certain contexts**, such as embedded feed readers or if the feed is opened directly in a browser. Setting the correct RSS/XML content type ensures browsers interpret the feed safely and reduces risk.\r\n\r\n### Affected Code\r\n\r\n```js\r\n// server/model/status_page.js\r\nresponse.send(await StatusPage.renderRSS(statusPage, slug));\r\n// No Content-Type override (defaults to text/html)\r\n```\r\n\r\n### Impact\r\n\r\n* Incorrect content type can lead to unsafe rendering in some browsers or feed readers\r\n* Low likelihood of XSS due to CDATA escaping, but setting a proper type mitigates potential risk\r\n* Affects anyone consuming the RSS feed in a browser context\r\n\r\nSeverity is assessed as **Low**, since user content is already escaped and the risk requires a specific client behavior.\r\n\r\n### Recommended Fix\r\n\r\n* Explicitly set the content type to a safe RSS/XML type:\r\n\r\n```js\r\nresponse.type('application/rss+xml');\r\n```\r\n\r\n* Ensure all user-controlled content remains properly escaped in CDATA sections\r\n* Optionally, apply a Content Security Policy (CSP) to further mitigate browser risks\r\n\r\n### CWE\r\n\r\n* **CWE-116** – Improper Encoding or Escaping of Output\r\n\r\n### References\r\n\r\n* OWASP XSS Prevention Cheat Sheet – CDATA in XML/RSS\r\n* RFC 822 / RSS Security Considerations\r\n\r\n### Credits\r\n\r\nReported by: Bugbunny.ai\n\nAffected packages: :uptime-kuma\nPatched: uptime-kuma 2.1.0","url":"https://github.com/louislam/uptime-kuma/security/advisories/GHSA-9fg7-wgm7-57fh","published_at":"2026-02-08T15:49:41Z","updated_at":"2026-02-08T15:49:41Z","fetched_at":"2026-11-22T13:40:14.883733Z","severity":"low","cvss_score":null,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":"GHSA-9fg7-wgm7-57fh","vuln_ids":["GHSA-9FG7-WGM7-57FH"],"tags":["repo-advisory","","CWE-79","security","repo:louislam/uptime-kuma"],"cluster_id":11318,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12013","html":"https://vulnwatch.ve1ve2.com/item/12013"}},{"id":12701,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"[SECURITY RELEASE] louislam/uptime-kuma 2.1.0","summary":"Fixes advisories: GHSA-9fg7-wgm7-57fh\n\nSecurity keywords: security\n\nChangelog:\r\n\r\nAll beta changes are also included in this release.\r\nPlease go throught them too, in total this relase had 250 PRs merged.\r\nhttps://github.com/louislam/uptime-kuma/releases/tag/2.1.0-beta.0\r\nhttps://github.com/louislam/uptime-kuma/releases/tag/2.1.0-beta.1\r\nhttps://github.com/louislam/uptime-kuma/releases/tag/2.1.0-beta.2\r\nhttps://github.com/louislam/uptime-kuma/releases/tag/2.1.0-beta.3\r\n\r\n### 🆕 New Features\r\n- #6830 feat(notification): add Jira Service Management as a notification provider (Thanks @jankal)\r\n- #6777 feat: add google sheets notification provider (Thanks @dharunashokkumar)\r\n\r\n### 💇‍♀️ Improvements\r\n- #6843 feat(discord): add custom message and format presets for notifications (Thanks @epifeny)\r\n- #6804 feat(ntfy): add custom title and message templates for notifications (Thanks @epifeny)\r\n\r\n### 🐞 Bug Fixes\r\n- #6845 fix: certificate expiry (use Settings.set instead of Settings.setSetting) (Thanks @epifeny)\r\n- #6841 fix: weblate conflict (Thanks @Aluisio @AnnAngela @cyril59310 @dodog @FunNikita @Kf637 @kurama @mafen @michi-onl @MrEddX @pmontp19)\r\n- #6835 feat(slack): Add option to include monitor group name in notifications (Thanks @dovansy1998)\r\n- #6822 fix: improve monitor list selection behavior (Thanks @frozenflux2)\r\n- #6805 fix: RSS pubDate timezone issue with backend test (#6422) (Thanks @Aqudi)\r\n- #6795 fix: monitor names hidden by tags (Thanks @bittoby)\r\n- #6792 fix: expand/collapse all groups now works with nested groups (Thanks @kurama)\r\n- #6791 Fix bot filtering in generate-changelog.mjs \r\n- #6789 fix: Add input validation for monitor ID in badge endpoints (Thanks @Angel98518)\r\n- #6783 fix: improve RADIUS client error handling and socket cleanup (Thanks @dive2tech)\r\n- #6778 fix: MongoDB monitor JSON.parse error handling (Thanks @Angel98518)\r\n\r\n### ⬆️ Security Fixes\r\n\r\n### 🦎 Translation Contributions\r\n- #6853 chore: Translations Update from Weblate (Thanks @2000Arion @Aluisio @AnnAngela @cyril59310 @dodog @jochemp264 @Kf637 @michi-onl @MrEddX)\r\n- #6834 feat(i18n): Add Bavarian German language support \r\n- #6817 Translations Update from Weblate (Thanks @Aluisio @AnnAngela @dodog @FunNikita @Kf637 @kurama @mafen @michi-onl @MrEddX @pmontp19)\r\n- #6597 chore: Translations Update from Weblate (Thanks @101br03k @2000Arion @aindriu80 @Aluisio @AndyLCQ @AnnAngela @atriwidada @bkzspam @Buchtic @cyril59310 @dodog @Donglingfeng @hackerpro17s @IsayIsee @isfan14 @ivanbratovic @JavierLuna @JWeinelt @Kodashas @michi-onl @MrEddX @simonghpub @superpep @tony-chompoo @Virenbar)\r\n- #6163 feat: add Globalping support (Thanks @radulucut)\r\n\r\n\r\n### Others\r\n- #6877 chore: npm update \r\n- #6875 chore: Update final release workflow \r\n- #6849 feat: Adding monitor_id and heartbeat_id to HaloPSA (Thanks @Yasindu20)\r\n- #6814 chore: Revert \"feat: added monitoring for postgres query result\" \r\n- #6787 chore: update to 2.1.0-beta.3 \r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n","url":"https://github.com/louislam/uptime-kuma/releases/tag/2.1.0","published_at":"2026-02-07T02:31:49Z","updated_at":null,"fetched_at":"2026-11-22T14:05:37.744921Z","severity":"low","cvss_score":null,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":"GHSA-9fg7-wgm7-57fh","vuln_ids":["GHSA-9FG7-WGM7-57FH"],"tags":["release","repo:louislam/uptime-kuma","security","stack","uptime-kuma"],"cluster_id":11318,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12701","html":"https://vulnwatch.ve1ve2.com/item/12701"}}]}