CVE-2021-43702: ASUS RT-A88U 3.0.0.4.386_45898 is vulnerable to Cross Site Scripting (XSS).
Noroxi assessment
Priority: Monitor (action score 36/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.97% (FIRST EPSS); higher than 62.3% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
ASUS RT-A88U 3.0.0.4.386_45898 is vulnerable to Cross Site Scripting (XSS). The ASUS router admin panel does not sanitize the WiFI logs correctly, if an attacker was able to change the SSID of the router with a custom payload, they could achieve stored XSS on the device.
- Published
- Jul 5, 2022
- Updated
- Jun 17, 2026
- EPSS
- 0.9% · 62th percentile
- CWE
- CWE-79
Report tools
Action score
36
Monitor
Low priority for now.
- CVSS
- 36 / 40 · 9.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.9%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| asus | zenwifi xd4s firmware | cpe:2.3:o:asus:zenwifi_xd4s_firmware |
| asus | zenwifi xd4s | cpe:2.3:h:asus:zenwifi_xd4s |
| asus | zenwifi xt9 firmware | cpe:2.3:o:asus:zenwifi_xt9_firmware |
| asus | zenwifi xt9 | cpe:2.3:h:asus:zenwifi_xt9 |
| asus | zenwifi xd5 firmware | cpe:2.3:o:asus:zenwifi_xd5_firmware |
| asus | zenwifi xd5 | cpe:2.3:h:asus:zenwifi_xd5 |
| asus | zenwifi pro et12 firmware | cpe:2.3:o:asus:zenwifi_pro_et12_firmware |
| asus | zenwifi pro et12 | cpe:2.3:h:asus:zenwifi_pro_et12 |
| asus | zenwifi pro xt12 firmware | cpe:2.3:o:asus:zenwifi__pro_xt12_firmware |
| asus | zenwifi pro xt12 | cpe:2.3:h:asus:zenwifi__pro_xt12 |
| asus | zenwifi ax hybrid firmware | cpe:2.3:o:asus:zenwifi_ax_hybrid_firmware |
| asus | zenwifi ax hybrid | cpe:2.3:h:asus:zenwifi_ax_hybrid |
and 174 more
Limit the impact of XSS
This is a cross-site scripting (XSS) vulnerability. A well-configured Content-Security-Policy doesn't fix it, but greatly reduces its impact. Check your site's CSP and other security headers for free.
Check security headersAffected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- asus 4g-ac53u firmware3.0.0.4.386.46061
- asus 4g-ac68u firmware3.0.0.4.386.46061
- asus rog rapture gt-ac2900 firmware3.0.0.4.386.46061
- asus rog rapture gt-ac5300 firmware3.0.0.4.386.46061
- asus rog rapture gt-ax11000 firmware3.0.0.4.386.46061
- asus rt-ac1200 firmware3.0.0.4.386.46061
- asus rt-ac1200e firmware3.0.0.4.386.46061
- asus rt-ac1200g firmware3.0.0.4.386.46061
- asus rt-ac1200g+ firmware3.0.0.4.386.46061
- asus rt-ac1200gu firmware3.0.0.4.386.46061
- asus rt-ac1200hp firmware3.0.0.4.386.46061
- asus rt-ac1300g+ firmware3.0.0.4.386.46061
- asus rt-ac1300uhp firmware3.0.0.4.386.46061
- asus rt-ac1750 b1 firmware3.0.0.4.386.46061
- asus rt-ac1750 firmware3.0.0.4.386.46061
- asus rt-ac1900 firmware3.0.0.4.386.46061
- asus rt-ac1900p firmware3.0.0.4.386.46061
- asus rt-ac1900u firmware3.0.0.4.386.46061
- asus rt-ac2200 firmware3.0.0.4.386.46061
- asus rt-ac2400 firmware3.0.0.4.386.46061
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.
No history yet (it accumulates with the daily EPSS job).
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
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- A user must open a link or visit a page.
- 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
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
nvd-primary
Root cause
User content is inserted into the page as HTML. The browser interprets the content as code rather than data.
The bug in code
The whole CWE-79 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
commentEl.innerHTML = comment.body;Fixed
commentEl.textContent = comment.body;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)
ATT&CK techniques
—
Change 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.