Anyone with a share link can RESET all website data in Umami
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (umami 2.3.1), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
npm umami
- Affected
- < 2.3.1
- Fixed in
- 2.3.1
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-8www-cffh-4q98 lists affected ranges: npm umami >=0 <2.3.1 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-8www-cffh-4q98 lists affected ranges: npm umami >=0 <2.3.1
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 9.6 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
Summary 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 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!
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-8www-cffh-4q98
- Revision 1 · created ·
Published from osv record GHSA-8www-cffh-4q98
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-8www-cffh-4q98 Advisory: Anyone with a share link can RESET all website data in Umami IDs: GHSA-8www-cffh-4q98 Record: https://patchnext.com/advisories/ghsa-8www-cffh-4q98 (revision 2, source checked 26 Oct 2026, 12:24 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Critical (CVSS 9.6) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: umami 2.3.1. A vendor fix does not mean a deployment is fixed. ## Affected components - npm umami: affected < 2.3.1; fixed in 2.3.1 ## Suggested inspection (read-only) - `npm ls umami --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on umami. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-8www-cffh-4q98 (OSV record GHSA-8www-cffh-4q98 lists affected ranges: npm umami >=0 <2.3.1 (fixed)) - Verified: https://github.com/advisories/GHSA-8www-cffh-4q98 (GitHub-reviewed advisory GHSA-8www-cffh-4q98 lists affected ranges: npm umami >=0 <2.3.1) Commands are suggestions: review each one before running it.
Loading voting…