Severity:

HIGH RISK

(7.3)

Unrestricted File Upload in Technostrobe HI-LED-WR120-G2

CVE-2026-5573

Analyzed

Vulnerability type

Category:

Unrestricted File Upload

CWE:

CWE-284, CWE-434

Impact:

Arbitrary File Upload and Potential Remote Compromise

Severity:

HIGH RISK

(7.3)

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 file upload handling weakness in Technostrobe HI-LED-WR120-G2 5.5.0.1R6.03.30 allows remote attackers to manipulate the cwd argument on the /fs endpoint, resulting in unrestricted file upload to the device's filesystem.

When exposed to untrusted networks, this flaw can enable attackers to place arbitrary files in sensitive locations, potentially leading to device compromise or persistent tampering with configuration and behavior.

Affected context

The vulnerability occurs in the file handling logic behind the /fs path of Technostrobe HI-LED-WR120-G2 firmware version 5.5.0.1R6.03.30.

It is relevant when the device's management or file system interface is network-accessible, particularly if it is reachable from untrusted networks or the public internet.

The issue appears when the cwd argument, which influences where files are written, is not sufficiently constrained or validated, allowing writes outside of intended directories or without adequate authorization checks.

Exploit preconditions

  • Attack surface: Network-exposed /fs endpoint on the Technostrobe HI-LED-WR120-G2 device.
  • Required access: Ability to send HTTP or protocol-specific requests to the /fs interface; no strong indication of prior authentication being required.
  • Trigger point: Submitting a request that manipulates the cwd parameter so that uploaded content is stored in unintended locations or bypasses normal file restrictions.
  • Why exploitation is possible: The file upload handler appears to trust the cwd argument and does not enforce strict access control, directory restrictions, or robust validation of upload destinations, leading to unrestricted file upload behavior.

Why this happens

At its core, the vulnerability stems from insufficient authorization and validation around where and how files can be written by remote clients.

The /fs handler appears to accept a client-controlled cwd parameter that influences file storage location without robust checks on the caller's rights (CWE-284: Improper Access Control) or on the permissibility of the target directory and file type (CWE-434: Unrestricted Upload of File with Dangerous Type).

This insecure design pattern treats client-supplied path or directory parameters as trustworthy, failing to enforce a strict, server-side-defined storage location and file policy.

As a result, remote users can cause arbitrary files to be created or overwritten in locations that may affect device behavior, integrity, or future code execution.

Potential impact

  • Placement of arbitrary files on the device's filesystem.
  • Overwriting existing files, including configuration or log files, leading to operational disruption.
  • Upload of script-like or executable content that may be leveraged for remote code execution, depending on how the device processes or serves files.
  • Establishment of persistence by placing files that alter startup behavior or scheduled tasks, if such mechanisms exist on the device.
  • Use of the device as a foothold within an operational network, including staging of further attacks or covert data storage.

General mitigation guidance

Mitigation efforts typically focus on tightening both access control and file handling semantics for upload functionality:

  • Restrict upload endpoints so they are only accessible from trusted management networks, employing network segmentation and access control lists.
  • Enforce strict server-side mapping of upload destinations: ignore client-supplied directory parameters like cwd and confine all uploads to predefined, non-executable directories.
  • Implement robust authorization checks so only authenticated and appropriately privileged users can perform file uploads, with clear separation of read and write capabilities.
  • Validate file characteristics (such as type, extension, and size) against an allowlist and avoid storing uploaded files in directories that the device serves or executes directly.
  • Run services handling uploads under least-privilege accounts and ensure file permissions do not grant broader access than required.
  • Where possible, treat uploaded content as data only and avoid any automatic interpretation or execution.

How teams detect issues like this

Effective detection strategies combine configuration review, code inspection, and runtime monitoring:

  • During code review, flag any upload or file management endpoints that rely on client-controlled parameters (like cwd, path, or filename) to determine file destinations, especially when coupled with weak or absent authorization checks.
  • Use static analysis rules to identify patterns such as direct concatenation of user input into filesystem paths and missing checks around authentication/authorization in file-handling routines.
  • Establish policies that require security review for any new file upload or management feature, including examination of directory whitelisting, file type enforcement, and privilege boundaries.
  • Monitor device logs for anomalous file operations, such as uploads to unexpected directories or unusually frequent write operations from the same remote source.
  • Employ network monitoring to detect suspicious patterns targeting the /fs endpoint, including repeated attempts to manipulate path-related parameters.

Sources

SourceLink
github.comgithub.com/shiky8/my--cve-vulnerability-research/blob/main/my_VulnDB_cves/CVE-TECHNOSTROBE-05-FileUpload.md
vuldb.comvuldb.com/submit/783326
vuldb.comvuldb.com/vuln/355343
vuldb.comvuldb.com/vuln/355343/cti

Frequently asked

questions

Yes. The description indicates that the attack can be launched remotely against the /fs endpoint, assuming the device's interface is reachable over the network.

The public information does not clearly specify authentication requirements. Given the description of "unrestricted upload" and the high severity, it is reasonable to treat the endpoint as potentially accessible with weak or no authentication until proven otherwise.

The most robust fix is to decouple upload destinations from client-controlled parameters, enforce strict server-side directory whitelisting, and require strong authentication and authorization for any file upload operations. Uploads should be confined to non-executable locations and validated against a strict file-type policy.

Design upload mechanisms with a zero-trust mindset toward client input: never use user-controlled values to select file paths, enforce least-privilege access controls on upload endpoints, rigorously validate file content and metadata, and incorporate security reviews and automated checks for any feature that writes to the filesystem.

Find out what's already
exploitable in your codebase.