NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

Attribute Injection leading to XSS(Cross-Site-Scripting)GHSA-v4v2-8h88-65qj

MEDIUMFix: louislam/uptime-kuma@f28dccf

GHSA-v4v2-8h88-65qj is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in uptime-kuma. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for uptime-kuma — see the affected versions and patch details below.

Also known asCVE-2023-49276
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs43th percentile — riskier than 43% of all scored CVEsHighest risk
0.00%0.34%0.68%1.03%0.5%0.5%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
uptime-kumanpm
144downloads / week

Description

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. image

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
  1. Click Save and return to the interface. XSS occurs. screenshots: image

9d0603e634fb7da2e83a0a45dc0a36ac

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmuptime-kuma≥ 1.20.0&&< 1.23.71.23.7npm install uptime-kuma@1.23.7

Affected Products

1 product · 1 configurations
Application
uptime kumauptime.kuma
≥ 1.20.0 && < 1.23.7
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Uptime Kuma is an open source self-hosted monitoring tool. In affected v…

github.comNVDDec 2023

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for uptime-kuma, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update uptime-kuma to 1.23.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v4v2-8h88-65qj is resolved across your whole dependency graph.

  3. Workarounds

    Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

### 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. ![image](https://user-images.githubusercontent.com/110759348/282278047-667b774b-421f-449a-8f95-3f3906ae4216.png) ### 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
O3 Security · Impact-Aware SCA

Is GHSA-v4v2-8h88-65qj in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Attribute Injection leading to XSS(Cross-Site-Scripting)