Rv320 FirmwareOperating system · Cisco

CVE-2019-1827

MEDIUM · 6.1 CVSS v3.0 Published 2019-04-04
Fix available
A fix is available. Upgrade to 1.4.2.22 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
A vulnerability in the Online Help web service of Cisco Small Business RV320 and RV325 Dual Gigabit WAN VPN Routers could allow an unauthenticated, remote attacker to conduct a reflected cross-site scripting (XSS) attack against a user of the service. The vulnerability exists because the Online Help web service of an affected device insufficiently validates user-supplied input. An attacker could exploit this vulnerability by persuading a user of the service to click a malicious link. A successful exploit could allow the attacker to execute arbitrary script code in the context of the affected service or access sensitive browser-based information.This vulnerability affects Cisco Small Business RV320 and RV325 Dual Gigabit WAN VPN Routers running firmware releases prior to 1.4.2.22.

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

Reflected cross-site scripting (XSS) vulnerability in the Online Help web service of Cisco Small Business RV320 and RV325 Dual Gigabit WAN VPN Routers. The web service insufficiently validates user-supplied input, allowing unauthenticated remote attackers to inject malicious script code via crafted URLs that get reflected back to users. Successful exploitation enables arbitrary script execution in the context of the affected service or access to sensitive browser-based information.

MitigationUpgrade Cisco Small Business RV320/RV325 routers to firmware release 1.4.2.22 or later. Prior to upgrading, back up the current configuration and test the new firmware in a lab environment to ensure all VPN and WAN functionalities operate correctly.

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
Rv320 FirmwareOperating system
Affected:< 1.4.2.22
Rv325 FirmwareOperating system
Affected:< 1.4.2.22

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/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 checks

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

  1. Confirm router model
    Access the router web interface, check the device label, or use the CLI command 'show version' to verify the model is Cisco RV320 or RV325
    Affected if Model is RV320 or RV325
  2. Retrieve firmware version
    Log into the router web interface and navigate to Status > System Summary, or use the CLI command 'show version' to obtain the current firmware build number
    Affected if Firmware version is below 1.4.2.22
  3. Verify Online Help service is enabled
    Attempt to access the help system via the router web interface by navigating to the help functionality or checking if /help/ endpoint responds
    Affected if Online Help web service is accessible and firmware is below 1.4.2.22

The router is affected if it is a Cisco RV320 or RV325 running firmware version prior to 1.4.2.22 with the Online Help web service exposed.

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.

From vendor data
Upgrade available Upgrade to 1.4.2.22 or later
Fixed in 1.4.2.22
Interim mitigation

Upgrade Cisco Small Business RV320/RV325 routers to firmware release 1.4.2.22 or later. Prior to upgrading, back up the current configuration and test the new firmware in a lab environment to ensure all VPN and WAN functionalities operate correctly.

Fix this in Rv320 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
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,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-1827 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-1827 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