CVE-2023-50737: An input validation vulnerability in the SE Menu allows an attacker to execute arbitrary code.
Noroxi assessment
Priority: Monitor (action score 36/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.96% (FIRST EPSS); higher than 62.3% of all records.
- Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Update when a fix is released; follow the vendor's advisory.
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
The SE menu contains information used by Lexmark to diagnose device errors. A vulnerability in one of the SE menu routines can be leveraged by an attacker to execute arbitrary code.
- Published
- Feb 27, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.9% · 62th percentile
- CWE
- CWE-20
Report tools
Action score
36
Low priority for now.
- CVSS
- 36 / 40 · 9.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.9%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Lexmark
- 9.1
- NVD has not scored this yet; the score shown is the CNA’s.
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
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi 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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| lexmark | cxtpc firmware | cpe:2.3:o:lexmark:cxtpc_firmware |
| lexmark | cstpc firmware | cpe:2.3:o:lexmark:cstpc_firmware |
| lexmark | mxtct firmware | cpe:2.3:o:lexmark:mxtct_firmware |
| lexmark | mxtpm firmware | cpe:2.3:o:lexmark:mxtpm_firmware |
| lexmark | cxtmm firmware | cpe:2.3:o:lexmark:cxtmm_firmware |
| lexmark | mslsg firmware | cpe:2.3:o:lexmark:mslsg_firmware |
| lexmark | mxlsg firmware | cpe:2.3:o:lexmark:mxlsg_firmware |
| lexmark | mslbd firmware | cpe:2.3:o:lexmark:mslbd_firmware |
| lexmark | mxlbd firmware | cpe:2.3:o:lexmark:mxlbd_firmware |
| lexmark | msngm firmware | cpe:2.3:o:lexmark:msngm_firmware |
| lexmark | mstgm firmware | cpe:2.3:o:lexmark:mstgm_firmware |
| lexmark | mxngm firmware | cpe:2.3:o:lexmark:mxngm_firmware |
and 38 more
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 various
- variousaffected
Same product
lexmark: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-50736A vulnerability has been identified in the PostScript interpreter in various Lexmark devices.36Monitor
- CVE-2023-50735A vulnerability has been identified in the PostScript interpreter in various Lexmark devices.36Monitor
- CVE-2023-50734A vulnerability has been identified in the PostScript interpreter in various Lexmark devices.36Monitor
Published before and after this one in the same product
- Later →CVE-2023-50733Jan 21, 2025 · A Server-Side Request Forgery (SSRF) vulnerability exists in newer Lexmark devices.34Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
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.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Sina KheirkhahSummoning Team reported this to ZDIfinder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2023-50733329 days apartA Server-Side Request Forgery (SSRF) vulnerability exists in newer Lexmark devices.34Monitor
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0140 · Feb 28, 2024(Lexmark Güvenlik Zafiyeti)
Not on record for this CVE: EPSS history · patch commit or PR link · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-20 · Improper Input ValidationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
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.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Server Side Include (SSI) InjectionCAPEC-101likelihood: High · High
- Cross Zone ScriptingCAPEC-104likelihood: Medium · High
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Double EncodingCAPEC-120likelihood: Low · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
ATT&CK techniques
- Obfuscated Files or InformationT1027
- Masquerading: Invalid Code SignatureT1036.001
- Steal Web Session CookieT1539
- Subvert Trust Controls: Code SigningT1553.002
- Impair Defenses:Impair Command History LoggingT1562.003
- Hijack Execution Flow:Dynamic Linker HijackingT1574.006
- Hijack Execution Flow:Path Interception by PATH Environment VariableT1574.007
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.