Skip to content
Security

WAVLINK WL-WN579A3-A, CVE-2026-120195: a new CVE scored 10

·5 min read

The bottom line

If you run a WAVLINK WL-WN579A3-A, find out this week whether its admin pages can be reached from the internet, and ask your supplier for a fixed firmware. If you do not run this model, you can stop reading.
Cover page of WAVLINK WL-WN579A3-A, CVE-2026-120195: a new CVE scored 10Free analysis report · 8 pagesWAVLINK WL-WN579A3-A, CVE-2026-120195: a new CVE scored 10The same note as a document you can keep or forward: what the sources say, who is affected, and what to do first.Download the analysis report →

At a glance

FactDetail
ProductWAVLINK WL-WN579A3-A (CVE-2026-120195)
SeverityCritical: 10 (CVSS 4.0)
StatusA new CVE record, published by VulDB on 1 November 2026. Not on CISA's list of exploited vulnerabilities when we read it on 1 November 2026, which means nothing public says yet that anyone is using it.
Fixed inNo source we read names a fixed version
Who looks firstAnyone running a WAVLINK WL-WN579A3-A on firmware 2026-03-10-94f93d4, and the IT provider who manages it, especially if its web admin pages can be reached from outside.

Does this apply to you?

Answer in order. Stop at the first no.
QuestionIf noIf yes
Do you run a WAVLINK WL-WN579A3-A?Nothing to do for this CVE.Check the firmware version (next question).
Does the device run firmware 2026-03-10-94f93d4?The record lists only that version. Ask WAVLINK or your supplier about yours.You are in the affected range. Check who can reach it.
Can the device's web admin pages be reached from the internet or from untrusted networks?Exposure is lower, but still plan to apply a fix once one exists.Restrict access now, then press your supplier for a fix.

What it is

The record says the setup wizard's handling of the wlan_ssid value lets an attacker make the device run operating system commands. It says the attack can be made remotely and that the exploit has been disclosed publicly.

Why it matters

The score is 10 out of 10, and the weakness ids are CWE-78 and CWE-77, both command injection. Our reading is that a device that runs an attacker's commands can be used to watch or redirect the traffic of everything behind it. The record also says the exploit is public, so waiting for a CISA listing is not a safe plan.

Exposure by situation

These priorities are our judgement from what the sources say about who can use the flaw and how. They are not vendor ratings.

Where you stand, and how soon
Your situationPriorityTimeframe
Affected firmware, admin pages reachable from the internetMediumThis week, before anything else
Affected firmware, admin pages reachable only from your internal networkMediumThis week; limit who can reach the admin pages
Affected firmware, admin pages reachable only from a small management networkLowNext patch cycle, once a fix exists
A different WAVLINK model or firmware versionLowAsk your supplier whether it is affected
You do not run this deviceNoneNone for this CVE

Things people will get wrong

  • "It is not on the CISA list, so nobody is using it." The record is new and CISA does not list it yet. The record itself says the exploit is public and may be used.
  • "There is a patch, so we are covered." No source we could read names a fixed version. Do not assume one exists until the vendor says so in writing.
  • "Only the setup wizard is affected, and we finished setup long ago." The record does not say the handler is switched off after setup. Treat the device as exposed until the vendor says otherwise.

How we would triage it

This is our judgement.

Step 1: Find the devices and versions you run

  • List every WAVLINK WL-WN579A3-A on your sites, including ones installed by others.
  • Read the firmware version from the device's admin page and compare it with 2026-03-10-94f93d4, the version the record lists.

Step 2: Reduce exposure

  • Make sure the admin pages cannot be reached from the internet, and turn off any remote management setting.
  • Allow admin access only from one trusted management address or network.

Step 3: Ask for a fix

  • The record says the vendor was contacted early, but no source names a fixed version. Ask WAVLINK or your supplier for one in writing.
  • If no fix is offered, consider replacing the device where it faces untrusted networks.

Step 4: Confirm the result

  • Once a fix is applied, read the firmware version again and record it.
  • Check that the admin pages are still not reachable from outside.

To close it, read the version from the product itself, not from an old inventory, and save the output with the date. If you cannot update today, write down who owns it, the new date, and what limits exposure until then.

Send this to your IT provider

Copy it, change the names and dates, and send it. It is a draft for you to check, not a template tested with any provider.

Hello, we are checking our exposure to CVE-2026-120195, a command injection flaw in the WAVLINK WL-WN579A3-A. The record says firmware 2026-03-10-94f93d4 is affected and that the exploit is public. Please tell us whether we run this model, where, and which firmware each unit has. Please confirm whether the admin pages can be reached from the internet. No fixed version is named in what we found, so please ask the vendor for one. Please send written confirmation of the versions and the fix, or of the steps taken to limit exposure, by the date you propose. Thank you.

The weakness behind it

The record classes this as CWE-78 and CWE-77.

The sources, in their words

The CVE record:

A security vulnerability has been detected in WAVLINK WL-WN579A3-A 2026-03-10-94f93d4. The impacted element is the function set_wzdgwMesh of the file /cgi-bin/adm.cgi of the component Initial Setup Wizard. The manipulation of the argument wlan_ssid leads to os command injection. The attack is possible to be carried out remotely. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure.

Versions of WAVLINK WL-WN579A3-A the record lists as affected:

  • 2026-03-10-94f93d4

What we do not know yet

  • Which firmware version, if any, fixes the flaw; no vendor page could be read.
  • Whether an attacker needs to log in first; the record does not say.
  • Whether the flaw is being used in real attacks; CISA does not list it yet.
  • Whether other firmware versions or WAVLINK models are affected.
  • Exploitation is not recorded. That is not the same as none.
  • This is a new record: scores, versions and wording can change in the first days, and they are as at 1 November 2026. We have not read the vendor's advisory page and we have not tested it.
  • The sections headed "The bottom line", "Does this apply to you?", "What it is", "Why it matters", "Exposure by situation", "Things people will get wrong", "How we would triage it" and "Send this to your IT provider" are our interpretation of the sources, not a statement by CISA or the vendor.

Does this touch your business?

A new vulnerability is a question about what you run, who can reach it and what it would cost you. If you want a person to answer it for your own systems, start with your IT setup.

Also worth reading

Start with one piece of work.

Give us one piece of work and read access to one system. We map it and come back with what we found, what we would build and what it would take — before any commitment. You decide using our output, not our pitch.

Talk to us