CVE-2023-49276
published 2023-12-01CVE-2023-49276: Uptime Kuma is an open source self-hosted monitoring tool. In affected versions the Google Analytics element in vulnerable to Attribute Injection leading to…
PriorityP425medium6.1CVSS 3.1
AVNACLPRNUIRSCCLILAN
EPSS
0.50%
38.8th percentile
Uptime Kuma is an open source self-hosted monitoring tool. In affected versions the Google Analytics element in vulnerable to Attribute Injection leading to Cross-Site-Scripting (XSS). Since the custom status interface can set an independent Google Analytics ID and the template has not been sanitized, there is an attribute injection vulnerability here, which can lead to XSS attacks. This vulnerability has been addressed in commit `f28dccf4e` which is included in release version 1.23.7. Users are advised to upgrade. There are no known workarounds for this vulnerability.
Affected
3 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| louislam | uptime-kuma | — | — |
| louislam | uptime-kuma | >= 1.20.0 < 1.23.7 | 1.23.7 |
| uptime.kuma | uptime_kuma | >= 1.20.0 < 1.23.7 | 1.23.7 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
Attribute Injection leading to XSS(Cross-Site-Scripting)
osv·2023-11-24
CVE-2023-49276 [MEDIUM] Attribute Injection leading to XSS(Cross-Site-Scripting)
Attribute Injection leading to XSS(Cross-Site-Scripting)
### Summary
Google Analytics element Attribute Injection leading to XSS
### Details
Since the custom status interface can set an independent Google Analytics ID and the template has not been sanitized, there is an attribute injection vulnerability here, which can lead to XSS attacks.
### PoC
1. Run the latest version of the louislam/uptime-kuma container and initialize the account password.
2. Create a new status page.
3. Edit the status page and change the Google Analytics ID to following payload(it only works for firefox. Any attribute can be injected, but this seems the most intuitive):
```
123123" onafterscriptexecute=alert(window.name+1),eval(window.name) a="x
```
4. Click Save and return to the interface. XSS occurs.
scree
GHSA
Attribute Injection leading to XSS(Cross-Site-Scripting)
ghsa·2023-11-24
CVE-2023-49276 [MEDIUM] CWE-79 Attribute Injection leading to XSS(Cross-Site-Scripting)
Attribute Injection leading to XSS(Cross-Site-Scripting)
### Summary
Google Analytics element Attribute Injection leading to XSS
### Details
Since the custom status interface can set an independent Google Analytics ID and the template has not been sanitized, there is an attribute injection vulnerability here, which can lead to XSS attacks.
### PoC
1. Run the latest version of the louislam/uptime-kuma container and initialize the account password.
2. Create a new status page.
3. Edit the status page and change the Google Analytics ID to following payload(it only works for firefox. Any attribute can be injected, but this seems the most intuitive):
```
123123" onafterscriptexecute=alert(window.name+1),eval(window.name) a="x
```
4. Click Save and return to the interface. XSS occurs.
scree
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://github.com/louislam/uptime-kuma/commit/f28dccf4e11f041564293e4f407e69ab9ee2277fhttps://github.com/louislam/uptime-kuma/security/advisories/GHSA-v4v2-8h88-65qjhttps://github.com/louislam/uptime-kuma/commit/f28dccf4e11f041564293e4f407e69ab9ee2277fhttps://github.com/louislam/uptime-kuma/security/advisories/GHSA-v4v2-8h88-65qj
2023-12-01
Published