Skip to content
Noroxi
NVD / CVE Program· CNA Lexmark

CVE-2025-9269: Server-Side Request Forgery (SSRF) vulnerability found in embedded web server

Noroxi assessment

Priority: Monitor (action score 27/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.33% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: Lexmark CX, XC, CS, MS, MX, XM, et. al. CSLBL.230.467 and later, CSLBN.230.467 and later, CSNGV.250.200 and later.

Low priority for now. Upgrade to Lexmark CX, XC, CS, MS, MX, XM, et. al. CSLBL.230.467 and later, CSLBN.230.467 and later, CSNGV.250.200 and later or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 6.9 · v4.0—No exploit Fix available
Published
Sep 9, 2025
Updated
Jun 17, 2026
EPSS
0.3% · 26th percentile

Report tools

JSON

Action score

27

Monitor

Low priority for now.

CVSS
27 / 40 · 6.9 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Lexmark
6.9
NVD has not scored this yet; the score shown is the CNA’s.

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-9269

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for lexmark records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Lexmark). Independent of NVD's CPE analysis and usually ahead of it.

  • Lexmark CX, XC, CS, MS, MX, XM, et. al.

    • up to and including CXTLS.250.199affectedfixed in CXTLS.250.200 and later
    • up to and including MXTLS.250.199affectedfixed in MXTLS.250.200 and later
    • up to and including CSTLS.250.199affectedfixed in CSTLS.250.200 and later
    • up to and including MSNSN.250.199affectedfixed in MSNSN.250.200 and later
    • up to and including MSTSN.250.199affectedfixed in MSTSN.250.200 and later
    • up to and including MXTSN.250.199affectedfixed in MXTSN.250.200 and later
    • up to and including CSNGV.250.199affectedfixed in CSNGV.250.200 and later
    • up to and including CSTGV.250.199affectedfixed in CSTGV.250.200 and later
    • up to and including CXTGV.250.199affectedfixed in CXTGV.250.200 and later
    • up to and including CXTPC.250.199affectedfixed in CXTPC.250.200 and later

Same product

lexmark: all records

Other highest-scoring records for the same primary product.

  • CVE-2025-1127Combination Path Traversal and Concurrent Execution vulnerability exists within the embedded web server
    36Monitor
  • CVE-2024-11344Type confusion vulnerability in the Postscript interpreter in various Lexmark devices
    29Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Lexmark CX, XC, CS, MS, MX, XM, et. al.CSLBL.230.467 and laterVendor (CNA)
Lexmark CX, XC, CS, MS, MX, XM, et. al.CSLBN.230.467 and laterVendor (CNA)
Lexmark CX, XC, CS, MS, MX, XM, et. al.CSNGV.250.200 and laterVendor (CNA)
Lexmark CX, XC, CS, MS, MX, XM, et. al.CSNZJ.250.200 and laterVendor (CNA)
Lexmark CX, XC, CS, MS, MX, XM, et. al.CSTAT.230.467 and laterVendor (CNA)
Lexmark CX, XC, CS, MS, MX, XM, et. al.CSTGV.250.200 and laterVendor (CNA)
Lexmark CX, XC, CS, MS, MX, XM, et. al.CSTLS.250.200 and laterVendor (CNA)
Lexmark CX, XC, CS, MS, MX, XM, et. al.CSTMH.230.467 and laterVendor (CNA)
Lexmark CX, XC, CS, MS, MX, XM, et. al.CSTMM.250.200 and laterVendor (CNA)
Lexmark CX, XC, CS, MS, MX, XM, et. al.CSTPC.250.200 and laterVendor (CNA)
Lexmark CX, XC, CS, MS, MX, XM, et. al.CSTPP.230.467 and laterVendor (CNA)
Lexmark CX, XC, CS, MS, MX, XM, et. al.CSTZJ.250.200 and laterVendor (CNA)
Lexmark CX, XC, CS, MS, MX, XM, et. al.CXLBL.230.467 and laterVendor (CNA)
Lexmark CX, XC, CS, MS, MX, XM, et. al.CXLBN.230.467 and laterVendor (CNA)
Lexmark CX, XC, CS, MS, MX, XM, et. al.CXNZJ.250.200 and laterVendor (CNA)
Lexmark CX, XC, CS, MS, MX, XM, et. al.CXTAT.230.467 and laterVendor (CNA)
Lexmark CX, XC, CS, MS, MX, XM, et. al.CXTGV.250.200 and laterVendor (CNA)
Lexmark CX, XC, CS, MS, MX, XM, et. al.CXTLS.250.200 and laterVendor (CNA)
Lexmark CX, XC, CS, MS, MX, XM, et. al.CXTMH.230.467 and laterVendor (CNA)
Lexmark CX, XC, CS, MS, MX, XM, et. al.CXTMM.250.200 and laterVendor (CNA)
Lexmark CX, XC, CS, MS, MX, XM, et. al.CXTPC.250.200 and laterVendor (CNA)
Lexmark CX, XC, CS, MS, MX, XM, et. al.CXTPP.230.467 and laterVendor (CNA)
Lexmark CX, XC, CS, MS, MX, XM, et. al.CXTZJ.250.200 and laterVendor (CNA)
Lexmark CX, XC, CS, MS, MX, XM, et. al.LW80.GM2.P261 and laterVendor (CNA)
Lexmark CX, XC, CS, MS, MX, XM, et. al.LW80.PRL.P261 and laterVendor (CNA)
Lexmark CX, XC, CS, MS, MX, XM, et. al.LW80.SB2.P261 and laterVendor (CNA)
Lexmark CX, XC, CS, MS, MX, XM, et. al.LW80.VY2.P261 and laterVendor (CNA)
Lexmark CX, XC, CS, MS, MX, XM, et. al.LW80.VYL.P261 and laterVendor (CNA)
Lexmark CX, XC, CS, MS, MX, XM, et. al.LW90.DN2.P225 and laterVendor (CNA)
Lexmark CX, XC, CS, MS, MX, XM, et. al.LW90.DN4.P225 and laterVendor (CNA)

+29

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
X

Weakness class (CWE)

CWE-918 · Server-Side Request Forgery (SSRF)

CVSS vector

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

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records