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

> Authenticated attackers can inject malicious scripts via the TMPL_INFO parameter, leading to arbitrary JavaScript execution in other users' browsers.

- **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:** 1 Dec 2025
- **Updated:** 1 Dec 2025
- **Also known as:** GHSA-wv2v-g4hw-ff7x

## What is CVE-2025-64030?

CVE-2025-64030 is a medium-severity cross-site scripting vulnerability in n/a, published on 1 Dec 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

Eximbills Enterprise 4.1.5 (Built on 2020-10-30) is vulnerable to authenticated stored cross-site scripting (CWE-79) via the /EximBillWeb/servlets/WSTrxManager endpoint. Unsanitized user input in the TMPL_INFO parameter is stored server-side and rendered to other users, enabling arbitrary JavaScript execution in their browsers.

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

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

It affects 1 product.


Products: Chinasystems Eximbills Enterprise.

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

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

## Is CVE-2025-64030 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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