Active debug code exists in Yamaha wireless LAN access point devices.
Active debug code exists in Yamaha wireless LAN access point devices. If a logged-in user who knows how to use the debug function accesses the device's management page, this function can be enabled by performing specific operations. As a result, an arbitrary OS command may be executed and/or configuration settings of the device may be altered. Affected products and versions are as follows: WLX222 firmware Rev.24.00.03 and earlier, WLX413 firmware Rev.22.00.05 and earlier, WLX212 firmware Rev.21.00.12 and earlier, WLX313 firmware Rev.18.00.12 and earlier, and WLX202 firmware Rev.16.00.18 and earlier.
- Published
- Jan 24, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 23th percentile
- CWE
- CWE-78
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
27
Monitor
Low priority for now.
- CVSS
- 27 / 40 · 6.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| yamaha | wlx222 firmware | cpe:2.3:o:yamaha:wlx222_firmware |
| yamaha | wlx222 | cpe:2.3:h:yamaha:wlx222 |
| yamaha | wlx413 firmware | cpe:2.3:o:yamaha:wlx413_firmware |
| yamaha | wlx413 | cpe:2.3:h:yamaha:wlx413 |
| yamaha | wlx212 firmware | cpe:2.3:o:yamaha:wlx212_firmware |
| yamaha | wlx212 | cpe:2.3:h:yamaha:wlx212 |
| yamaha | wlx313 firmware | cpe:2.3:o:yamaha:wlx313_firmware |
| yamaha | wlx313 | cpe:2.3:h:yamaha:wlx313 |
| yamaha | wlx202 firmware | cpe:2.3:o:yamaha:wlx202_firmware |
| yamaha | wlx202 | cpe:2.3:h:yamaha:wlx202 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- yamaha wlx202 firmwarebefore 16.00.19
- yamaha wlx212 firmwarebefore 21.00.13
- yamaha wlx222 firmwarebefore 24.00.04
- yamaha wlx313 firmwarebefore 18.00.13
- yamaha wlx413 firmwarebefore 22.00.06
Versions reported by the vendor
Affected version ranges reported by the assigning authority (jpcert). Independent of NVD's CPE analysis and usually ahead of it.
Yamaha Corporation WLX202
- firmware Rev.16.00.18 and earlieraffected
Yamaha Corporation WLX212
- firmware Rev.21.00.12 and earlieraffected
Yamaha Corporation WLX222
- firmware Rev.24.00.03 and earlieraffected
Yamaha Corporation WLX313
- firmware Rev.18.00.12 and earlieraffected
Yamaha Corporation WLX413
- firmware Rev.22.00.05 and earlieraffected
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Adjacent
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-78 · Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')CVSS vector
CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
User input is inserted as text into a shell command. The shell may interpret special characters in the input as part of the command.
The bug in code
The whole CWE-78 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const host = req.body.host;exec("ping -c 1 " + host, onResult);Fixed
const host = req.body.host;if (!/^[a-z0-9.-]{1,253}$/i.test(host)) return res.sendStatus(400);execFile("ping", ["-c", "1", host], onResult);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Command DelimitersCAPEC-15likelihood: High · High
- Exploiting Multiple Input Interpretation LayersCAPEC-43likelihood: Medium · High
- Argument InjectionCAPEC-6likelihood: High · High
- OS Command InjectionCAPEC-88likelihood: High · High
ATT&CK techniques
—
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.