dbcve.org
Inrouter 900 FirmwareOperating system · Inhandnetworks

CVE-2022-27280

MEDIUM · 5.4 CVSS v3.1 Published 2022-04-10
Fix available
A fix is available. Upgrade to 1.0.0.r11700 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
InHand Networks InRouter 900 Industrial 4G Router before v1.0.0.r11700 was discovered to contain a stored cross-site scripting (XSS) vulnerability via the web_exec parameter at /apply.cgi.

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 confidence

A stored cross-site scripting (XSS) vulnerability exists in the web_exec parameter at /apply.cgi on InHand Networks InRouter 900 Industrial 4G Router firmware versions prior to v1.0.0.r11700. Authenticated attackers can inject malicious JavaScript code that persists on the device and executes when other users access the affected interface.

MitigationUpgrade the device firmware to v1.0.0.r11700 or later. Additionally, implement proper input validation and output encoding on the web_exec parameter to prevent XSS attacks.

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
Inrouter 900 FirmwareOperating system
Affected:< 1.0.0.r11700

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Access the device web interface or CLI and confirm the model is InRouter 900. In the web interface, this is typically displayed on the status or device info page. Via CLI, use 'show version' or check the system information.
    Affected if The device is not an InHand Networks InRouter 900 model.
  2. Check the firmware version
    Navigate to the device web interface status page or use the CLI command 'show version' to retrieve the current firmware version. Compare this version against the affected range of < 1.0.0.r11700.
    Affected if The installed firmware version is lower than 1.0.0.r11700.
  3. Verify the web management interface is enabled
    In the device web interface, confirm that the HTTP/HTTPS management access is enabled. This can typically be found under System Settings > Network Services or similar. Check if /apply.cgi is accessible.
    Affected if The web management interface is disabled, as the vulnerability requires access to /apply.cgi.
  4. Confirm authentication access exists
    Determine if any user accounts with access to /apply.cgi exist on the device. The vulnerability requires an authenticated session to inject the payload via the web_exec parameter.
    Affected if No authenticated users have access to the web interface, or the web_exec parameter is not present in the configuration.

The device is affected if it is an InHand Networks InRouter 900 running firmware version lower than 1.0.0.r11700, has the web management interface enabled, and has users with access to the /apply.cgi endpoint.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.0.0.r11700 or later
Fixed in 1.0.0.r11700
Interim mitigation

Upgrade the device firmware to v1.0.0.r11700 or later. Additionally, implement proper input validation and output encoding on the web_exec parameter to prevent XSS attacks.

Recommended fix High confidence

1.0.0.r11700

  1. Backup the current router configuration before starting the upgrade process
  2. Download the fixed firmware version 1.0.0.r11700 from the official InHand Networks support website or authorized distribution channel
  3. Access the InRouter 900 web management interface
  4. Navigate to the firmware upgrade section (typically under System or Administration settings)
  5. Upload the firmware file 1.0.0.r11700 and initiate the upgrade
  6. Wait for the upgrade process to complete - do not power off the device during this process
  7. After the router restarts, log back into the web interface
  8. Verify the firmware version displayed matches 1.0.0.r11700
Caveat Firmware upgrades may temporarily disrupt connectivity; ensure maintenance window and test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Inrouter 900 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-27280 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-27280 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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