dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2025-9269

MEDIUM · 6.9 CVSS v4.0 Published 2025-09-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 Server-Side Request Forgery (SSRF) vulnerability has been identified in the embedded web server in various Lexmark devices. This vulnerability can be leveraged by an attacker to force the device to send an arbitrary HTTP request to a third-party server. Successful exploitation of this vulnerability can lead to internal network access / potential data disclosure from a device.

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 confidence

This is a Server-Side Request Forgery (SSRF) vulnerability in the embedded web server of Lexmark devices. An attacker can exploit this to force the device to send arbitrary HTTP requests to third-party servers, potentially allowing internal network reconnaissance and data disclosure.

MitigationApply vendor patches when available; until then, network segmentation and firewall rules restricting outbound connections from affected devices can limit exposure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 Lexmark device model
    Access the device's web interface or check the device label/menu to confirm it is a Lexmark product. Note the exact model number.
    Affected if The device is not a Lexmark product - this CVE applies only to Lexmark devices.
  2. Locate firmware version
    Log into the Lexmark embedded web server (EWS) and navigate to the 'Settings' or 'About' page to find the firmware version. Alternatively, print a configuration page from the device control panel.
    Affected if The firmware version cannot be determined - without a version, you cannot compare against fixed releases.
  3. Confirm web server is enabled
    Access the device's network settings via the web interface or control panel and verify that the Embedded Web Server (EWS) is enabled and accessible over HTTP/HTTPS.
    Affected if The embedded web server is disabled and not accessible - the SSRF attack surface is not present.
  4. Check for outbound HTTP request logging
    Review device logs or network traffic logs for any suspicious outbound HTTP requests originating from the device to unfamiliar external IP addresses or domains.
    Affected if Unexpected outbound HTTP requests to third-party servers are observed - this may indicate active exploitation.
  5. Verify network exposure
    Determine if the Lexmark device's web interface is exposed to untrusted networks (such as the internet or guest networks) by reviewing firewall rules and access control lists.
    Affected if The web server is directly accessible from untrusted networks - the attack vector is exposed.

A user is affected if they have a Lexmark device with an accessible embedded web server, and the device can make outbound HTTP requests to third-party servers without user consent.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches when available; until then, network segmentation and firewall rules restricting outbound connections from affected devices can limit exposure.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-9269 — 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-2025-9269 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