CVE-2025-3508
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 · uneditedCertain HP DesignJet products may be vulnerable to information disclosure though printer's web interface allowing unauthenticated users to view sensitive print job information.
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 confidenceHP DesignJet printers contain an unauthenticated information disclosure vulnerability in their embedded web server. The web interface allows remote attackers to access sensitive print job information—including document names, user identifiers, timestamps, and potentially partial document content—without any authentication credentials.
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< jgr9_09_25_22.1< jgr9_09_25_22.1< jgr9_09_25_22.1< jgr9_09_25_22.1< jgrw_09_25_22.1< jgrw_09_25_22.1< jgrw_09_25_22.1< jgrw_09_25_22.1CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/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.
-
Identify printer model and firmware versionOpen a web browser and navigate to the printer's IP address to access the embedded web server. Locate the 'About' or 'Support' page in the web interface to find the product code (e.g., W3z72e, W6b55a) and current firmware version.Affected if The product code matches one of the affected codes (W3z72e, W3z72f, W3z72g, W3z72h, W6b55a, W6b55b, W6b55c, W6b55d) AND the firmware version is earlier than jgr9_09_25_22.1 (for W3z72x models) or jgrw_09_25_22.1 (for W6b55x models).
-
Confirm web server is accessibleAttempt to access the printer's web interface by entering its IP address in a web browser. Verify that the HP DesignJet web page loads without requiring login credentials.Affected if The web interface loads and is accessible without any authentication, indicating the vulnerability condition exists for that specific version.
-
Check remote web management statusIn the printer's web interface, navigate to the 'Network' or 'Security' settings section. Look for options related to 'Remote Web Management' or 'Embedded Web Server' configuration to determine if web access is enabled.Affected if Remote web management is enabled and the printer is reachable over the network, making it potentially exploitable.
-
Verify network exposureCheck if the printer's IP address is accessible from outside the local network by reviewing firewall rules, router configurations, or network scans. Use 'netstat' or similar tools on a local host to confirm open ports (typically 80/443) on the printer's IP.Affected if The printer's web interface is exposed to untrusted networks (e.g., directly accessible from the internet or guest networks), increasing exploitability.
A defender is affected if their HP DesignJet matches one of the listed product codes AND runs firmware older than jgr9_09_25_22.1 or jgrw_09_25_22.1 AND has its web interface accessible without authentication.
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 · scopedRestrict network access to the printer's web interface using firewall rules or network segmentation, disable remote web management if not required, and apply vendor patches when available.
W3z72e/f/g/h: upgrade to firmware jgr9_09_25_22.1 | W6b55a/b/c/d: upgrade to firmware jgrw_09_25_22.1
- 1. Identify your HP DesignJet model number (W3z72e, W3z72f, W3z72g, W3z72h, W6b55a, W6b55b, W6b55c, or W6b55d)
- 2. Check the current firmware version by accessing the printer's web interface or printing a configuration page
- 3. Navigate to HP Support at support.hp.com and search for your specific HP DesignJet model
- 4. Locate the firmware download section and download the fixed firmware version (jgr9_09_25_22.1 for W3z72x models or jgrw_09_25_22.1 for W6b55x models)
- 5. Access the printer's web interface as an administrator
- 6. Navigate to the Firmware Update or Setup section
- 7. Upload and apply the downloaded firmware file
- 8. Verify the firmware upgrade was successful by checking the firmware version again
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2025-3508 — 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-2025-3508 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