Lexmark CX/XC/CS/MS/MX/XM up to TZJ.240.205 Embedded Web Server server-side request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Lexmark CX, XC, CS, MS, MX and XM. This vulnerability affects unknown code of the component Embedded Web Server. The manipulation leads to server-side request forgery. This vulnerability is documented as CVE-2025-9269. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability, which was classified as critical, has been found in Lexmark CX, XC, CS, MS, MX and XM. This issue affects some unknown functionality of the component Embedded Web Server. The manipulation with an unknown input leads to a server-side request forgery vulnerability. Using CWE to declare the problem leads to CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. Impacted is confidentiality. The summary by CVE is:
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.
The weakness was released by Chen. The advisory is shared at lexmark.com. The identification of this vulnerability is CVE-2025-9269 since 08/20/2025. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/09/2025).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
- LBD.240.407
- LBL.240.407
- LBN.240.407
- LSG.240.407
- NGM.240.205
- NGV.240.205
- NGW.240.205
- NSN.240.205
- NZJ.240.205
- TAT.240.407
- TCT.240.205
- TGM.240.205
- TGV.240.205
- TGW.240.205
- TLS.240.205
- TMH.240.407
- TMM.240.205
- TPC.240.205
- TPM.240.205
- TPP.240.407
- TSN.240.205
- TZJ.240.205
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Server-side request forgeryCWE: CWE-918
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
08/20/2025 CVE reserved09/09/2025 Advisory disclosed
09/09/2025 VulDB entry created
09/09/2025 VulDB entry last update
Sources
Advisory: lexmark.comResearcher: Chen
Status: Confirmed
CVE: CVE-2025-9269 (🔒)
GCVE (CVE): GCVE-0-2025-9269
GCVE (VulDB): GCVE-100-323381
Entry
Created: 09/09/2025 23:05Changes: 09/09/2025 23:05 (67)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.