cve.bz

CVE-2025-1680 moxa

0.0 infoEPSS 0.2%

Info (0.0) in moxa. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

0.0 none
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:N/VA:N/SC:N/SI:N/SA:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 9th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-10-23. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-349 Acceptance of Extraneous Untrusted Data With Trusted Data
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2025-1680 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-1680?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-1680?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-1680 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2025-1680

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2025-1680](https://cve.bz/cve/badge/CVE-2025-1680.svg)](https://cve.bz/cve/CVE-2025-1680)

HTML:

<a href="https://cve.bz/cve/CVE-2025-1680"><img src="https://cve.bz/cve/badge/CVE-2025-1680.svg" alt="CVE-2025-1680"></a>

Affected

  • moxa:tn-4500a series
  • moxa:tn-5500a series
  • moxa:tn-g4500 series
  • moxa:tn-g6500 series

Versions

From the CNA's record in the CVE List.

ProductAffected
Moxa TN-4500A Seriesfrom 1.0 through 3.13
Moxa TN-5500A Seriesfrom 1.0 through 3.13
Moxa TN-G4500 Seriesfrom 1.0 through 5.5
Moxa TN-G6500 Seriesfrom 1.0 through 5.5

Attack patterns (CAPEC)

  • CAPEC-75 Manipulating Writeable Configuration Files Likelihood: High · Severity: Very High
  • CAPEC-141 Cache Poisoning Likelihood: High · Severity: High
  • CAPEC-142 DNS Cache Poisoning Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON