CVE-2026-5573
Received Received - Intake
Unrestricted File Upload via cwd Manipulation in Technostrobe HI-LED-WR120-G

Publication date: 2026-04-05

Last updated on: 2026-04-30

Assigner: VulDB

Description
A weakness has been identified in Technostrobe HI-LED-WR120-G2 5.5.0.1R6.03.30. This impacts an unknown function of the file /fs. Executing a manipulation of the argument cwd can lead to unrestricted upload. The attack can be launched remotely. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-04-05
Last Modified
2026-04-30
Generated
2026-05-07
AI Q&A
2026-04-05
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
technostrobe hi-led-wr120-g2_firmware 5.5.0.1r6.03.30
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-434 The product allows the upload or transfer of dangerous file types that are automatically processed within its environment.
CWE-284 The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

The CVE-2026-5573 vulnerability affects the Technostrobe HI-LED-WR120-G2 obstruction lighting controller, a device used to control aviation safety lighting on tall structures. The device runs an embedded Linux-based web server with a POST /fs endpoint that allows unauthenticated users to upload files to any directory on the device’s filesystem.

This upload functionality lacks authentication, file type validation, and path restrictions, enabling attackers to upload arbitrary files anywhere, including the web root directory. Attackers can manipulate the 'cwd' parameter to specify the upload directory, potentially overwriting critical system or configuration files.

The vulnerability allows remote attackers to upload malicious scripts or files without any credentials, which can then be accessed or executed to gain full control over the device.


How can this vulnerability impact me? :

This vulnerability can lead to unauthorized and unrestricted file uploads on a safety-critical device controlling aviation obstruction lighting. Attackers can upload malicious scripts or backdoors, leading to full operating system compromise.

  • Attackers can overwrite configuration files or install persistent backdoors.
  • They can disable or modify obstruction lighting, creating aviation safety hazards.
  • Full remote code execution on the device is possible, allowing attackers to control the lighting controller.
  • Such compromise can lead to regulatory violations and severe safety risks.

How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

This vulnerability impacts compliance primarily in the context of aviation safety and operational technology regulations rather than data privacy standards like GDPR or HIPAA.

Unauthorized control over obstruction lighting can violate regulations from aviation authorities such as the FAA, ICAO, and Transport Canada, which require reliable and secure lighting control to ensure safety.

While GDPR and HIPAA focus on personal data protection, this vulnerability's critical impact is on safety and operational compliance in aviation infrastructure.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by checking for the presence of the vulnerable POST /fs endpoint on the Technostrobe HI-LED-WR120-G2 device. An unauthenticated POST request to /fs with a multipart/form-data body including the cwd parameter and a file upload can confirm the vulnerability.

A suggested command to test the vulnerability is using curl to upload a test file to the device, for example:

If the file becomes accessible via HTTP GET (e.g., http://<device-ip>/http/Technostrobe/test.txt) without authentication, the device is vulnerable.


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include:

  • Enforce authentication for all file upload operations to prevent unauthenticated access.
  • Restrict the cwd parameter to a safe, server-controlled directory to prevent arbitrary file placement.
  • Implement strict allowlists for file extensions, allowing only safe types such as .cfg, .csv, or .json.
  • Store uploaded files outside the web root directory to prevent direct HTTP access.
  • Remove or disable the /fs upload endpoint if it is not required in production.

Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart