# CVE-2022-25256: Cross-site scripting in n/a

> Cross-site scripting in SAS Web Report Studio allows attackers to execute arbitrary JavaScript via malicious URL parameters, potentially leading to session hijacking.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **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:** 19 Feb 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-f94m-q2w2-2g64

## What is CVE-2022-25256?

CVE-2022-25256 is a medium-severity cross-site scripting vulnerability in n/a, published on 19 Feb 2022. 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

SAS Web Report Studio 4.4 allows XSS. /SASWebReportStudio/logonAndRender.do has two parameters: saspfs_request_backlabel_list and saspfs_request_backurl_list. The first one affects the content of the button placed in the top left. The second affects the page to which the user is directed after pressing the button, e.g., a malicious web page. In addition, the second parameter executes JavaScript, which means XSS is possible by adding a javascript: URL.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2022-25256?

It affects 1 product.


Products: Sas Web Report Studio.

## How do I fix CVE-2022-25256?

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

## Is CVE-2022-25256 being exploited?

There is no known exploitation of CVE-2022-25256 in the wild and no public exploit code.

Public exploit code:

- https://github.com/RobertDra/CVE-2022-25256 (github_poc): https://github.com/RobertDra/CVE-2022-25256

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-25256 and fix it if it is affected.

What it is: CVE-2022-25256 is a medium-severity cross-site scripting vulnerability in n/a, published on 19 Feb 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-25256 in the wild and no public exploit code.

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-2022-25256/ (Markdown: https://insights.sbomify.com/CVE-2022-25256/index.md)
```

## Sources

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

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