CVE-2026-5570

Technostrobe Hi-led-wr120-g2 Firmware authentication bypass

7.3 HIGHPublic exploitEPSS 0.99%

Published5 Apr 2026

Description

A vulnerability was determined in Technostrobe HI-LED-WR120-G2 5.5.0.1R6.03.30. The affected element is the function index_config of the file /LoginCB. This manipulation causes improper authentication. It is possible to initiate the attack remotely. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityLow

IntegrityLow

AvailabilityLow

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Affected products

Technostrobe Hi-led-wr120-g2 Firmware5.5.0.1r6.03.30

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

https://github.com/shiky8/my--cve-vulnerability-research/blob/main/my_VulnDB_cves/CVE-TECHNOSTROBE-02-AuthBypass.mdExploitMitigationThird Party Advisory
https://vuldb.com/submit/783323Third Party AdvisoryVDB Entry
https://vuldb.com/vuln/355340Third Party AdvisoryVDB Entry
https://vuldb.com/vuln/355340/ctiPermissions RequiredVDB Entry

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2026-5570 being actively exploited?

CVE-2026-5570 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.99%.

How severe is CVE-2026-5570?

CVE-2026-5570 has a CVSS 3.1 base score of 7.3, rated high. EPSS estimates a 0.99% probability of exploitation.

Which products are affected by CVE-2026-5570?

Affected products include Technostrobe Hi-led-wr120-g2 Firmware.

How do I fix CVE-2026-5570?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-5570 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.