CVE-2019-18914
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 potential security vulnerability has been identified for certain HP printers and MFPs that would allow redirection page Cross-Site Scripting in a client’s browser by clicking on a third-party malicious link.
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 confidenceThis is a reflected Cross-Site Scripting (XSS) vulnerability in the web interface of certain HP printers and MFPs. The vulnerability exists in a redirection page, where malicious JavaScript can be injected via a crafted URL containing the payload. When a user clicks on a third-party malicious link, the script executes in the user's browser in the context of the printer's web application.
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< 2309025_582081< 2309025_582098< 2309025_582089< 2309025_582096< 2309025_582102< 2309025_582099< 2309025_582093< 2309025_582101< 2309025_582084< 2309025_582108< 2309025_582106< 2309025_582097< 2410028_055010< 2410028_055028< 2410028_055035< 2410028_055034< 2410028_055015< 2410028_055019< 2410028_055002< 2410028_055018< 2410028_055020< 2410028_055026< 2410028_055041< 2410028_055006CVSS 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.1/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 checksWork through these to decide whether this CVE applies to you.
-
Verify HP printer web interface is accessibleAttempt to access the printer's web interface by entering the printer's IP address in a web browser. If a login page or HP printer interface loads, the web interface is enabled.Affected if The web interface is accessible and no authentication is required or the attacker can trick an authenticated user into clicking a malicious link.
-
Determine the Futuresmart firmware versionLog into the printer web interface and navigate to the 'General' or 'About' page (usually found under Settings, System Administration, or a similar section). Locate the firmware version field. The version typically appears as a long numeric string such as '2309025_582081' or '2410028_055010'.Affected if The firmware version displayed is a Futuresmart 3 or Futuresmart 4 build number.
-
Compare Futuresmart 3 version against affected buildsIf the firmware starts with '2309025_582', compare the numeric suffix against the affected list: 582081, 582098, 582089, 582096, 582102, 582099, 582093, 582101, 582084, 582108, 582106, 582097. If your suffix is LOWER than any of these values, the device is vulnerable.Affected if The installed Futuresmart 3 build number is less than any of the listed affected build numbers.
-
Compare Futuresmart 4 version against affected buildsIf the firmware starts with '2410028_055', compare the numeric suffix against the affected list: 055010, 055028, 055035, 055034, 055015, 055019, 055002, 055018, 055020, 055026, 055041, 055006. If your suffix is LOWER than any of these values, the device is vulnerable.Affected if The installed Futuresmart 4 build number is less than any of the listed affected build numbers.
-
Identify if redirection parameter is exploitable (optional)If the web interface is accessible, inspect URLs containing redirection parameters (such as 'dest=' or 'redirect='). Attempt a safe test by navigating to a URL like 'https://[PRINTER_IP]/hp/device/webProxy?dest=javascript:alert(1)' to see if the reflected parameter executes JavaScript.Affected if The URL parameter is reflected without sanitization and executes injected JavaScript code in the browser.
Your printer is affected if it runs Futuresmart 3 or Futuresmart 4 firmware with a build number lower than those listed in the affected versions AND the printer web interface is accessible to attackers or trick users into clicking malicious links.
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 data2309025_5820812309025_5820842309025_582089
Apply the appropriate HP firmware update or patch for affected printer models. As a compensating control, implement network segmentation to isolate printers and educate users about not clicking untrusted links targeting printer interfaces.
- Consultation3.0 h
- Implementation2.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,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-18914 — 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-2019-18914 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