CVE-2024-44414
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 · uneditedA vulnerability was discovered in FBM_292W-21.03.10V, which has been classified as critical. This issue affects the sub_4901E0 function in the msp_info.htm file. Manipulation of the path parameter can lead to command injection.
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 confidenceA command injection vulnerability exists in the FBM_292W-21.03.10V router firmware. The path parameter in the msp_info.htm file's sub_4901E0 function is not properly sanitized before being used in a system call, allowing remote attackers to inject and execute arbitrary shell commands.
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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 modelCheck the router label, web interface system info page, or boot logs for the exact model number FBM_292WAffected if The device is an FBM_292W router
-
Check the firmware versionAccess the router web interface, navigate to the system status or firmware upgrade page, and record the installed firmware version. Compare against 21.03.10VAffected if The firmware version is 21.03.10V or earlier
-
Locate the vulnerable web pageAccess the router web interface and attempt to reach the msp_info.htm page (typically at /msp_info.htm or similar path under the web management URL)Affected if The msp_info.htm page is accessible and responds to requests
-
Verify the sub_4901E0 function is presentExamine the msp_info.htm page source or decompile the firmware binary to confirm the sub_4901E0 function exists and processes the path parameterAffected if The sub_4901E0 function handles the path parameter without sanitization
-
Confirm web management interface is enabledCheck if the router HTTP/HTTPS web management interface is listening on the LAN or WAN interface by scanning the relevant ports (commonly 80 or 443)Affected if The web interface is exposed and the vulnerable parameter can be reached
You are affected if you have an FBM_292W router running firmware version 21.03.10V or earlier, and the msp_info.htm web page with the vulnerable sub_4901E0 function is accessible.
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 input validation and sanitization to the path parameter, replace unsafe system calls with safe APIs, and update to a patched firmware version when available.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-44414 — 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-44414 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