CVE-2024-36103
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 · uneditedOS command injection vulnerability in WRC-X5400GS-B v1.0.10 and earlier, and WRC-X5400GSA-B v1.0.10 and earlier allows a network-adjacent attacker with an administrative privilege to execute arbitrary OS commands by sending a specially crafted request to the product.
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 confidenceOS command injection vulnerability in WRC-X5400GS-B and WRC-X5400GSA-B wireless routers (firmware v1.0.10 and earlier) allows a network-adjacent attacker with administrative credentials to execute arbitrary OS commands by sending a specially crafted HTTP request to the device's web management interface.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Adjacent
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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 the device modelLog into the router web management interface and navigate to the Status or System Information page to confirm the exact model number (WRC-X5400GS-B or WRC-X5400GSA-B)Affected if The device model is WRC-X5400GS-B or WRC-X5400GSA-B
-
Check the installed firmware versionIn the web management interface, locate the firmware version in the Status, System, or About section; compare against the affected version v1.0.10Affected if The firmware version is v1.0.10 or earlier
-
Verify web management interface accessibilityCheck router firewall settings to determine if the web management interface (HTTP/HTTPS on ports 80/443) is accessible from WAN or untrusted networks rather than LAN onlyAffected if The administrative web interface is exposed to untrusted network segments or the internet
-
Review administrative account securityCheck that strong, unique passwords are configured for admin accounts and that default credentials have been changedAffected if Default administrative credentials are in use or weak passwords are set
-
Inspect access logs for suspicious requestsExamine the router's system logs or access logs for unusual or unexpected HTTP requests, particularly those containing shell metacharacters (|, ;, &, $ , `)Affected if Logs show suspicious HTTP requests with command injection patterns or unauthorized administrative access attempts
You are affected if the device is a WRC-X5400GS-B or WRC-X5400GSA-B router running firmware v1.0.10 or earlier with its web management interface accessible to untrusted networks.
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 dataApply vendor firmware update when available; until then, restrict administrative interface access to trusted networks only, use strong unique administrative credentials, and monitor for suspicious requests.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36103 — 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-36103 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