CVE-2023-23560 in the critical feed json
In certain Lexmark products through 2023-01-12, SSRF can occur because of a lack of input validation.
published 2023-01-23 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-27660
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 13.9%
- EPSS 13.9% chance of exploitation in 30 days, percentile 96%
- public exploits
- 0
- none known
Summary
In certain Lexmark products through 2023-01-12, SSRF can occur because of a lack of input validation.
Patch / fix
- lexmark b2236_firmware mslsg.081.234
- lexmark b2338_firmware msngm.081.234
- lexmark b2442_firmware msngm.081.234
- lexmark b2546_firmware msngm.081.234
- lexmark b2650_firmware msngm.081.234
- lexmark b2865_firmware msngw.081.234
- lexmark b3340_firmware mslbd.081.234
- lexmark b3442_firmware mslbd.081.234
- lexmark c2240_firmware cstzj.081.234
- lexmark c2325_firmware csnzj.081.234
- lexmark c2326_firmware cslbn.081.234
- lexmark c2425_firmware csnzj.081.234
- lexmark c2535_firmware csnzj.081.234
- lexmark c3224_firmware cslbl.081.234
- lexmark c3326_firmware cslbl.081.234
- lexmark c3426_firmware cslbn.081.234
- lexmark c4150_firmware cstat.081.234
- lexmark c6160_firmware cstpp.081.234
- lexmark c9235_firmware cstmh.081.234
- lexmark cs331_firmware cslbl.081.234
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 19 mo ago
Exploit prediction
13.87% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Classification
References
-
support.lexmark.com
/alerts/
vendor-advisory
-
publications.lexmark.com
/publications/security-alerts/CVE-2023-23560.pdf
vendor-advisory
Sources
- CVE List CVE-2023-23560
- NVD CVE-2023-23560
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.