/

CVE-2025-26238

Severity:

HIGH RISK

(8.1)

Code Injection (CWE-94) in D-Link DI-8100G msp_info

CVE-2025-26238

Deferred

Vulnerability type

Category:

Code Injection

CWE:

CWE-94

Impact:

Arbitrary Code Execution

Severity:

HIGH RISK

(8.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A high-severity code injection vulnerability in the D-Link DI-8100G allows malicious input supplied through the msp_info flag parameter to influence code execution. If an attacker can reach the affected interface and provide crafted input, the device may execute unauthorized commands with the privileges of the vulnerable service.

Affected context

The vulnerability occurs in D-Link DI-8100G firmware 17.12.20A1 when the msp_info component processes the flag parameter without sufficiently separating data from executable operations. Risk depends on whether the affected management or service interface is reachable and whether supplied values are trusted or adequately constrained.

Exploit preconditions

  • Attack surface: The msp_info interface or function that accepts the flag parameter - Required access: Network access or another permitted path to submit input to the affected component - Trigger point: Processing of the flag parameter by the vulnerable service - Why exploitation is possible: Input may reach an execution-sensitive operation without adequate validation, neutralization, or safe parameter handling

Why this happens

The underlying bug is an unsafe data-to-code boundary in which a parameter intended to represent a value can affect executable behavior. This pattern maps to CWE-94, Improper Control of Generation of Code, because externally influenced input is incorporated into an execution path without sufficiently restricting its syntax, meaning, or effects. The weakness is distinct from ordinary input validation failures when the resulting behavior can cause code to be generated or executed.

Potential impact

  • An attacker may execute unauthorized code on the affected device.
  • Device configuration or operational behavior could be altered.
  • Sensitive information accessible to the service could be exposed.
  • The device could be used to access or attack other systems on connected networks.
  • Availability could be reduced through service disruption or resource abuse.

General mitigation guidance

Mitigation generally focuses on eliminating code execution from parameter handling wherever possible. Secure-by-default designs treat flag values as data, use fixed allowlists or typed arguments, and pass parameters through APIs that do not invoke shells or dynamic interpreters. Input trust should be reduced through strict validation, canonicalization, and rejection of unexpected values. Management interfaces should be isolated, access controlled, and exposed only where necessary. Running services with least privilege and minimizing their filesystem and network permissions can limit consequences if a related flaw is reached.

How teams detect issues like this

Detection can include static analysis for user-controlled values flowing into command execution, dynamic evaluation, shell invocation, or code-generation APIs. Code reviews should examine flag parsing, string concatenation, escaping, and any implicit conversion from configuration data to executable operations. Runtime monitoring can alert on unexpected child processes, shell launches, unusual management requests, or changes initiated by the device service. Policy enforcement in build and deployment pipelines can prohibit unsafe execution APIs and require allowlisted parameter handling. Automated review tools may help identify these data-flow patterns.

Sources

SourceLink
github.comgithub.com/REYu6/iot/blob/main/CVE/dlink/DI_8100G-17.12.20A1.md/DI_8100G-17.12.20A1.md

Frequently asked

questions

Exploitability depends on network exposure and access controls around the

affected msp_info interface. It may be remotely reachable when that interface

is exposed to an attacker.

The attacker must be able to submit or influence the flag parameter. Whether

authentication is required depends on the device's deployment and interface

configuration.

Treat the flag value strictly as data, validate it against an allowlist, and

avoid shell, dynamic evaluation, or other execution-sensitive APIs.

Use typed and constrained parameter handling, review data flows into execution

functions, restrict management-plane exposure, and apply least privilege to

device services.

Find out what's already
exploitable in your codebase.