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

> An attacker can inject malicious scripts into the router's schedule page, potentially hijacking user sessions or executing code in the victim's browser.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:A/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:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Feb 2025
- **Updated:** 28 Feb 2025
- **Also known as:** GHSA-3r3m-77rh-j78q

## What is CVE-2025-25429?

CVE-2025-25429 is a medium-severity cross-site scripting vulnerability in n/a, published on 28 Feb 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Trendnet TEW-929DRU 1.0.0.10 contains a Stored Cross-site Scripting (XSS) vulnerability via the r_name variable inside the have_same_name function on the /addschedule.htm page.

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

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

It affects 1 product.


Products: Trendnet Tew-929dru Firmware.

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

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

## Is CVE-2025-25429 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-25428](https://insights.sbomify.com/CVE-2025-25428/): Hardcoded credentials in n/a (high 8.0)
- [CVE-2025-25430](https://insights.sbomify.com/CVE-2025-25430/): Cross-site scripting in n/a (medium 4.8)
- [CVE-2025-25431](https://insights.sbomify.com/CVE-2025-25431/): Cross-site scripting in n/a (medium 4.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-25429 is a medium-severity cross-site scripting vulnerability in n/a, published on 28 Feb 2025. It can only be exploited from the same machine or local 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-25429 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-25429/ (Markdown: https://insights.sbomify.com/CVE-2025-25429/index.md)
```

## Sources

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

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