Skip to main content
VulnerabilityPublished Updated

CVE-2025-41717: Phoenix Contact TC ROUTER 3002T-3G · Code Injection

Affects Phoenix Contact TC ROUTER 3002T-3GSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High : upgrade to 3.08.8 soon.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.08.8, 1.06.23, 3.07.7
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade TC ROUTER 3002T-3G and TC ROUTER 2002T-3G and TC ROUTER 3002T-4G and TC ROUTER 3002T-4G GL and TC ROUTER 3002T-4G VZW and TC ROUTER 3002T-4G ATT and TC ROUTER 2002T-4G and TC CLOUD CLIENT 1002-4G ATT to 3.08.8; TC ROUTER 5004T-5G EU to 1.06.23; CLOUD CLIENT 1101T-TX/TX and TC CLOUD CLIENT 1002-TX/TX to 3.07.7.

Affected software

ProductAffectedFixed in
Phoenix ContactTC ROUTER 3002T-3GAffected
  • <3.08.8
Fixed in
  • 3.08.8
Phoenix ContactTC ROUTER 2002T-3GAffected
  • <3.08.8
Fixed in
  • 3.08.8
Phoenix ContactTC ROUTER 3002T-4GAffected
  • <3.08.8
Fixed in
  • 3.08.8
Phoenix ContactTC ROUTER 3002T-4G GLAffected
  • <3.08.8
Fixed in
  • 3.08.8
Phoenix ContactTC ROUTER 5004T-5G EUAffected
  • <1.06.23
Fixed in
  • 1.06.23
Phoenix ContactTC ROUTER 3002T-4G VZWAffected
  • <3.08.8
Fixed in
  • 3.08.8

AI-suggested

  1. Immediately restrict access to the config-upload endpoint by implementing network segmentation and firewall rules to limit exposure only to trusted management networks.
  2. Enforce strict user training and awareness programs to prevent social engineering attacks that could trick privileged users into uploading malicious configurations.
  3. Implement multi-factor authentication and role-based access controls for all management interfaces to reduce the risk of unauthorized actions.
  4. Monitor network traffic and device logs for unusual upload activities or configuration changes indicative of exploitation attempts.
  5. Use intrusion detection/prevention systems (IDS/IPS) with signatures or heuristics targeting suspicious config-upload behaviors.
  6. Where possible, disable or restrict the config-upload functionality if not required operationally.
  7. Engage with Phoenix Contact for updates on patches or firmware upgrades and plan for rapid deployment once available.
  8. Consider deploying compensating controls such as application whitelisting or endpoint protection on devices connected downstream to detect and prevent malicious activity stemming from compromised routers.
  9. Conduct regular security audits and penetration tests focusing on industrial network devices to identify and remediate similar vulnerabilities proactively.

Description

An unauthenticated remote attacker can trick a high privileged user into uploading a malicious payload via the config-upload endpoint, leading to code injection as root. This results in a total loss of confidentiality, availability and integrity due to improper control of code generation ('Code Injection’).

References

Community reviews

Loading reviews…