CVE-2026-105284

Totolink A3002MU Authentication Check boa sub_40FCFC improper authorization

  • Critical 10.0
  • A public exploit reference is listed

Description

A weakness has been identified in Totolink A3002MU 1.0.0-B20230403.1455. The impacted element is the function sub_40FCFC of the file /bin/boa of the component Authentication Check. Executing a manipulation can lead to improper authorization. The attack may be launched remotely. The exploit has been made available to the public and could be used for attacks.

Key facts

Published
5 Oct 2026
Last changed
5 Oct 2026
Assigned by
VulDB
EPSS
0.828% likely to be exploited in the next 30 days, higher than 58.072% of CVEs (scores for 15 Nov 2026)
SSVC (CISA)
Exploitation: poc; Automatable: yes; Technical impact: total

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 10.0CVSS 4.0, Criticalfrom the CNA (VulDB)CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P
  • 10.0CVSS 3.1, Criticalfrom the CNA (VulDB)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H/E:P/RL:X/RC:R
  • 10.0CVSS 3.0, Criticalfrom the CNA (VulDB)CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H/E:P/RL:X/RC:R
  • 10.0CVSS 2.0, Highfrom the CNA (VulDB)AV:N/AC:L/Au:N/C:C/I:C/A:C/E:POC/RL:ND/RC:UR

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
TotolinkA3002MU
  • 1.0.0-B20230403.1455 (affected)

Timeline

  1. 4 Oct 2026 VulDB entry created
  2. 5 Oct 2026 Advisory disclosed
  3. 5 Oct 2026 VulDB entry last update
  4. 5 Oct 2026 Published

Weakness

References