# CVE-2023-24724: Cross-site scripting in n/a

> Stored XSS in SAS Admin Console allows attackers to inject scripts via user management fields, potentially leading to session hijacking or malicious actions.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Apr 2023
- **Updated:** 18 Feb 2025
- **Also known as:** GHSA-7fg2-xxpc-hg8m

## What is CVE-2023-24724?

CVE-2023-24724 is a medium-severity cross-site scripting vulnerability in n/a, published on 3 Apr 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A stored cross site scripting (XSS) vulnerability was discovered in the user management module of the SAS 9.4 Admin Console, due to insufficient validation and sanitization of data input into the user creation and editing form fields. The product name is SAS Web Administration interface (SASAdmin). For the product release, the reported version is 9.4_M2 and the fixed version is 9.4_M3. For the SAS release, the reported version is 9.4 TS1M2 and the fixed version is 9.4 TS1M3.

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

## Which versions are affected by CVE-2023-24724?

It affects 1 product.


Products: Sas Web Administration Interface.

## How do I fix CVE-2023-24724?

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

## Is CVE-2023-24724 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-24724 and fix it if it is affected.

What it is: CVE-2023-24724 is a medium-severity cross-site scripting vulnerability in n/a, published on 3 Apr 2023. Any signed-in user can exploit it over the network, 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-2023-24724 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-2023-24724/ (Markdown: https://insights.sbomify.com/CVE-2023-24724/index.md)
```

## Sources

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

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