CVE-2026-24433
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedShenzhen Tenda W30E V2 firmware versions up to and including V16.01.0.19(5037) contain a stored cross-site scripting vulnerability in the user creation functionality. Insufficient input validation allows attacker-controlled script content to be stored and later executed when administrative users access the affected management pages.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceStored cross-site scripting vulnerability in the Tenda W30E V2 router firmware user creation functionality. The device fails to properly sanitize input in the user creation parameters, allowing malicious JavaScript to be embedded in user account data and stored on the device. When administrative users access the management user list pages, the stored payload executes in their authenticated browser session.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 16.01.0.19\(5037\)CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify device model and firmware versionAccess the router web management interface (typically at http://192.168.0.1) and navigate to System Status or Firmware Version page. Alternatively, use command line: curl http://192.168.0.1/goform/getSysInfo or check via SNMP if available.Affected if Device is a Tenda W30E or W30E V2 with firmware version 16.01.0.19(5037) or lower
-
Confirm firmware version is within affected rangeCompare the identified firmware version number to the affected range: any version <= 16.01.0.19(5037) is vulnerable. Check the exact version string displayed in the router admin panel under System > Device Info or equivalent.Affected if Firmware version displayed is 16.01.0.19(5037) or any version number lower than this
-
Verify user management functionality is accessibleLog into the router web interface and navigate to the User Management, User Account, or Admin Users section (typically under System Management or Advanced Settings). Confirm the user creation or user list page is reachable without errors.Affected if User management interface is accessible and displays user list or user creation form
-
Inspect existing user accounts for suspicious contentIn the User Management page, examine each user account name/username field for any unexpected characters, scripts, or anomalies that may indicate a previously injected payload. Check for angle brackets, script tags, or encoded content.Affected if Any user account names contain HTML tags, script tags, or JavaScript-like content (e.g., <script>, onerror=, javascript:)
If the device is a Tenda W30E with firmware version 16.01.0.19(5037) or lower AND the user management interface is accessible, the environment is potentially affected by this stored XSS vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to a firmware version beyond V16.01.0.19(5037) that implements proper input validation and output encoding in the user creation functionality.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24433 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-24433 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data