CVE-2024-36491
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 · uneditedFutureNet NXR series, VXR series and WXR series provided by Century Systems Co., Ltd. allow an administrative user to execute an arbitrary OS command, obtain and/or alter sensitive information, and cause a denial-of-service (DoS) condition.
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 confidenceCommand injection vulnerability in FutureNet NXR, VXR, and WXR series routers allows authenticated administrative users to execute arbitrary OS commands, potentially leading to full system compromise, data exfiltration, and denial of service.
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< 7.4.10all versions< 21.14.11c< 21.12.10< 21.15.6< 6.23.11< 21.7.32< 21.15.2cCVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 router model and firmware versionAccess the router web interface or CLI and navigate to the system status or firmware information page. Look for the device model number (NXR 1300, 155/c, 610x, G050, G060, G100, G110, G120) and the installed firmware version string.Affected if The device is a Centurysys FutureNet NXR series model and the firmware version falls below the fixed versions: NXR 1300 < 7.4.10, NXR 610x < 21.14.11c, NXR G050 < 21.12.10, NXR G060 < 21.15.6, NXR G100 < 6.23.11, NXR G110 < 21.7.32, NXR G120 < 21.15.2c, or NXR 155/c of any version.
-
Confirm administrative web interface is accessibleAttempt to access the router administrative web interface via HTTP/HTTPS on the default management IP address. Verify that the login page loads and accepts credentials.Affected if The administrative web interface is reachable from network segments that include untrusted users, indicating potential exposure to the command injection flaw.
-
Check if SSH or telnet management is enabledFrom a remote location, attempt to connect to the router on common management ports (SSH typically port 22, telnet typically port 23) using the administrative IP address.Affected if SSH or telnet management interfaces are exposed to untrusted networks, allowing authenticated administrative access that could trigger the command injection.
-
Verify administrative access controlsReview the router access control list or management interface binding settings in the web interface under System > Administration or similar sections. Check if management interfaces are bound to specific IP addresses or VLANs.Affected if Management interfaces are bound to all interfaces (0.0.0.0) or accessible from WAN/outside segments rather than being restricted to trusted internal IPs only.
The environment is affected if the router is a Centurysys FutureNet NXR series model running a firmware version within the affected ranges AND the administrative interface (web, SSH, or telnet) is accessible from untrusted network segments.
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.
dbcve · scoped6.23.117.4.1021.7.32
Restrict administrative access to trusted IPs only, implement network segmentation, and apply vendor firmware patches when available. Consider disabling unnecessary administrative interfaces if not required for operations.
Upgrade to vendor-provided fixed firmware: NXR-1300: >=7.4.10, NXR-610x: >=21.14.11c, NXR-G050: >=21.12.10, NXR-G060: >=21.15.6, NXR-G100: >=6.23.11, NXR-G110: >=21.7.32, NXR-G120: >=21.15.2c. For NXR-155/c contact vendor directly.
- 1. Identify the exact FutureNet NXR model number (e.g., NXR-1300, NXR-610x, etc.)
- 2. Check the current firmware version via the device admin interface or CLI
- 3. Download the corresponding fixed firmware from Century Systems Co., Ltd. official support website
- 4. Backup the current device configuration before upgrading
- 5. Upload and install the fixed firmware version: For NXR-1300 use 7.4.10+, for NXR-610x use 21.14.11c+, for NXR-G050 use 21.12.10+, for NXR-G060 use 21.15.6+, for NXR-G100 use 6.23.11+, for NXR-G110 use 21.7.32+, for NXR-G120 use 21.15.2c+
- 6. For NXR-155/c (all versions), contact vendor for available patched firmware
- 7. Restore the configuration after upgrade
- 8. Verify the upgrade was successful and the command injection vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.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,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36491 — 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-36491 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