# CVE-2025-57424: Cross-site scripting in n/a

> Stored XSS in MyCourts allows attackers to hijack sessions and gain elevated access due to missing HttpOnly flags on cookies.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/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:** 29 Sep 2025
- **Updated:** 29 Sep 2025
- **Also known as:** GHSA-g389-gg4p-5w9j

## What is CVE-2025-57424?

CVE-2025-57424 is a high-severity cross-site scripting vulnerability in n/a, published on 29 Sep 2025. 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 exists in the MyCourts v3 application within the LTA number profile field. An attacker can insert arbitrary JavaScript into their profile, which executes in the browser of any user viewing it, including administrators. Due to the absence of the HttpOnly flag on the session cookie, this flaw could be exploited to capture session tokens and hijack user sessions, enabling elevated access.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-1004 (Sensitive Cookie Without 'HttpOnly' Flag)

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


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

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

## Is CVE-2025-57424 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-57424 is a high-severity cross-site scripting vulnerability in n/a, published on 29 Sep 2025. 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-2025-57424 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-57424/ (Markdown: https://insights.sbomify.com/CVE-2025-57424/index.md)
```

## Sources

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

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