CVE-2024-9477
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 · uneditedImproper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in AirTies Air4443 Firmware allows Cross-Site Scripting (XSS). This issue affects Air4443 Firmware: through 14102024. NOTE: The vendor was contacted and it was learned that the product classified as End-of-Life and End-of-Support.
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 · moderate confidenceCross-site scripting (XSS) vulnerability in AirTies Air4443 firmware allows attackers to inject malicious scripts through unsanitized input that gets rendered in web pages. The CVSS 6.1 indicates a network-attackable XSS with user interaction required, likely a stored or reflected variant affecting the router's web management interface.
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<= 14102024CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Determine the Air4443 firmware versionLog into the router's web management interface (typically at 192.168.1.1) and navigate to the Status or Firmware Upgrade page to view the current firmware version. Alternatively, check the version sticker on the device or consult your router's documentation for CLI access via telnet/SSH to run 'cat /proc/version' or similar version commands.Affected if The displayed firmware version is 14102024 or any earlier version number.
-
Verify web management interface accessibilityConfirm the router's web interface is reachable on the local network. Check if port 80 or 443 is open on the device IP. Determine whether the interface is exposed to the internet or untrusted networks by reviewing port forwarding rules, NAT settings, or firewall configurations.Affected if The web management interface is accessible from beyond the local trusted network (e.g., WAN side).
-
Compare installed version to affected rangeIf you obtained a firmware version number in step 1, compare it numerically or sequentially to 14102024. Note that version formats may vary (e.g., 1.41.02024 or similar). Document the exact version string for reference.Affected if The installed firmware version is less than or equal to 14102024.
-
Identify XSS injection points in the web interfaceInspect common input fields in the router's web interface such as network names (SSID), device hostnames, PPPoE credentials, or administrative usernames. These fields often store and render user-supplied values without proper sanitization, making them potential XSS vectors.Affected if Any of these input fields accept and reflect special characters (<, >, ", ', <script>) back into the rendered HTML without encoding.
You are affected if the Air4443 firmware version is 14102024 or earlier AND the web management interface is accessible, as the unsanitized input fields in the web UI can be exploited for XSS attacks.
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 dataSince the product is End-of-Life with no vendor patch, implement compensating controls such as WAF rules to block XSS payloads, network segmentation to isolate the device, or replace the device with a supported model. User awareness to avoid clicking suspicious links reduces exploitability.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-9477 — 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-2024-9477 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