CVE-2025-41717: CWE-94 Improper Control of Generation of Code ('Code Injection') in Phoenix Contact TC ROUTER 3002T-3G
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’).
AI Analysis
Technical Summary
CVE-2025-41717 is a vulnerability classified under CWE-94 (Improper Control of Generation of Code) found in the Phoenix Contact TC ROUTER 3002T-3G. The flaw allows an unauthenticated remote attacker to exploit the config-upload endpoint by tricking a high privileged user into uploading a malicious configuration payload. This payload, when processed by the device, results in arbitrary code execution with root privileges. The vulnerability arises because the device does not properly validate or sanitize the uploaded configuration data, enabling code injection. The attack vector is network-based (AV:N), requires no privileges (PR:N), but does require user interaction (UI:R), such as convincing an authorized user to perform the upload. The scope is unchanged (S:U), meaning the impact is confined to the vulnerable component. The consequences are severe, with complete compromise of confidentiality, integrity, and availability (C:H/I:H/A:H). This could lead to unauthorized control over the router, interception or manipulation of network traffic, disruption of network services, and potential pivoting into industrial control systems connected to the router. The vulnerability was publicly disclosed in January 2026, with no patches currently available. Although no exploits are known in the wild, the ease of exploitation and high impact make this a critical threat. The affected product is widely used in industrial and critical infrastructure environments, increasing the risk profile for organizations relying on this hardware.
Potential Impact
For European organizations, the impact of CVE-2025-41717 is substantial, particularly for those in industrial automation, manufacturing, energy, and critical infrastructure sectors where Phoenix Contact routers are deployed. Successful exploitation can lead to full device compromise, allowing attackers to intercept sensitive data, disrupt communications, or launch further attacks within the network. The loss of confidentiality could expose proprietary or operational data, while integrity violations could manipulate control commands or configurations, potentially causing physical damage or operational failures. Availability loss could disrupt critical services, leading to downtime and financial losses. Given the router's role as a network gateway, attackers could also use compromised devices as footholds for lateral movement, threatening broader organizational networks. The requirement for user interaction means social engineering or phishing attacks may be leveraged, increasing the attack surface. The lack of available patches exacerbates the risk, necessitating immediate compensating controls. Overall, the vulnerability poses a high risk to operational continuity and security posture of European entities using this product.
Mitigation Recommendations
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.
Affected Countries
Germany, France, Italy, Netherlands, Belgium, Sweden, Finland, Poland, Czech Republic, Austria
CVE-2025-41717: CWE-94 Improper Control of Generation of Code ('Code Injection') in Phoenix Contact TC ROUTER 3002T-3G
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’).
AI-Powered Analysis
Technical Analysis
CVE-2025-41717 is a vulnerability classified under CWE-94 (Improper Control of Generation of Code) found in the Phoenix Contact TC ROUTER 3002T-3G. The flaw allows an unauthenticated remote attacker to exploit the config-upload endpoint by tricking a high privileged user into uploading a malicious configuration payload. This payload, when processed by the device, results in arbitrary code execution with root privileges. The vulnerability arises because the device does not properly validate or sanitize the uploaded configuration data, enabling code injection. The attack vector is network-based (AV:N), requires no privileges (PR:N), but does require user interaction (UI:R), such as convincing an authorized user to perform the upload. The scope is unchanged (S:U), meaning the impact is confined to the vulnerable component. The consequences are severe, with complete compromise of confidentiality, integrity, and availability (C:H/I:H/A:H). This could lead to unauthorized control over the router, interception or manipulation of network traffic, disruption of network services, and potential pivoting into industrial control systems connected to the router. The vulnerability was publicly disclosed in January 2026, with no patches currently available. Although no exploits are known in the wild, the ease of exploitation and high impact make this a critical threat. The affected product is widely used in industrial and critical infrastructure environments, increasing the risk profile for organizations relying on this hardware.
Potential Impact
For European organizations, the impact of CVE-2025-41717 is substantial, particularly for those in industrial automation, manufacturing, energy, and critical infrastructure sectors where Phoenix Contact routers are deployed. Successful exploitation can lead to full device compromise, allowing attackers to intercept sensitive data, disrupt communications, or launch further attacks within the network. The loss of confidentiality could expose proprietary or operational data, while integrity violations could manipulate control commands or configurations, potentially causing physical damage or operational failures. Availability loss could disrupt critical services, leading to downtime and financial losses. Given the router's role as a network gateway, attackers could also use compromised devices as footholds for lateral movement, threatening broader organizational networks. The requirement for user interaction means social engineering or phishing attacks may be leveraged, increasing the attack surface. The lack of available patches exacerbates the risk, necessitating immediate compensating controls. Overall, the vulnerability poses a high risk to operational continuity and security posture of European entities using this product.
Mitigation Recommendations
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.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- CERTVDE
- Date Reserved
- 2025-04-16T11:17:48.313Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6965faafa60475309f41c759
Added to database: 1/13/2026, 7:56:31 AM
Last enriched: 2/5/2026, 8:02:54 AM
Last updated: 2/7/2026, 5:27:47 AM
Views: 95
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.