# CVE-2025-1680: Open redirect in TN-4500A Series

> Administrative users can inject Host headers to redirect users or forge links, enabling phishing attacks on Moxa Ethernet switches.

- **Severity:** Not scored
- **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:** 23 Oct 2025
- **Updated:** 23 Oct 2025
- **Also known as:** GHSA-8fj5-vvv3-q47w

## What is CVE-2025-1680?

CVE-2025-1680 is a vulnerability in Moxa TN-4500A Series, published on 23 Oct 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

An acceptance of extraneous untrusted data with trusted data vulnerability has been identified in Moxa’s Ethernet switches, which allows attackers with administrative privileges to manipulate HTTP Host headers by injecting a specially crafted Host header into HTTP requests sent to an affected device’s web service. This vulnerability is classified as Host Header Injection, where invalid Host headers can manipulate to redirect users, forge links, or phishing attacks. There is no impact to the confidentiality, integrity, and availability of the affected device; no loss of confidentiality, integrity, and availability within any subsequent systems.

Weakness: CWE-349 (Acceptance of Extraneous Untrusted Data With Trusted Data)

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


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

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

## Is CVE-2025-1680 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-1680 is a vulnerability in Moxa TN-4500A Series, published on 23 Oct 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-1680 in the wild and no public exploit code.

Affected product: Moxa TN-4500A Series. 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-1680/ (Markdown: https://insights.sbomify.com/CVE-2025-1680/index.md)
```

## Sources

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

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