# CVE-2025-28244: Information disclosure in n/a

> Remote attackers can steal user session tokens from local storage in Alteryx Server, enabling account takeover.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Jul 2025
- **Updated:** 11 Jul 2025
- **Also known as:** GHSA-v487-q9c3-h72w

## What is CVE-2025-28244?

CVE-2025-28244 is a high-severity vulnerability in n/a, published on 10 Jul 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Insecure Permissions vulnerability in the Local Storage in Alteryx Server 2023.1.1.460 allows remote attackers to obtain valid user session tokens from localStorage, leading to account takeover

Weakness: CWE-922 (Insecure Storage of Sensitive Information)

## Which versions are affected by CVE-2025-28244?

It affects 1 product.


Products: Alteryx Alteryx Server.

## How do I fix CVE-2025-28244?

No fix has been published for CVE-2025-28244 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-28244 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-28244 exists.

## Other vulnerabilities in n/a

- [CVE-2025-28243](https://insights.sbomify.com/CVE-2025-28243/): Cross-site scripting in n/a (high 8.0)
- [CVE-2025-28245](https://insights.sbomify.com/CVE-2025-28245/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2025-63291](https://insights.sbomify.com/CVE-2025-63291/): Missing authorization in n/a (medium 5.4)
- [CVE-2023-26961](https://insights.sbomify.com/CVE-2023-26961/): File upload in n/a (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-28244 and fix it if it is affected.

What it is: CVE-2025-28244 is a high-severity vulnerability in n/a, published on 10 Jul 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-28244 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-28244/ (Markdown: https://insights.sbomify.com/CVE-2025-28244/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-28244
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-28244
- OSV: https://osv.dev/vulnerability/CVE-2025-28244

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-28244/
Summaries are generated and may contain mistakes; the official description above is the record.