CVE-2023-22960: Lexmark products through 2023-01-10 have Improper Control of Interaction Frequency.
Noroxi assessment
Priority: Monitor (action score 38/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 27.9% (FIRST EPSS); higher than 98.1% of all records.
- 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.
- According to the record, no fixed version is available yet.
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
- Published
- Jan 23, 2023
- Updated
- Jun 17, 2026
- EPSS
- 27.9% · 98th percentile
- CWE
- CWE-307
Report tools
Action score
38
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 8 / 30 · 27.9%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
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 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 | b2236 firmware | cpe:2.3:o:lexmark:b2236_firmware |
| lexmark | b2236 | cpe:2.3:h:lexmark:b2236 |
| lexmark | b2338 firmware | cpe:2.3:o:lexmark:b2338_firmware |
| lexmark | b2338 | cpe:2.3:h:lexmark:b2338 |
| lexmark | b2442 firmware | cpe:2.3:o:lexmark:b2442_firmware |
| lexmark | b2442 | cpe:2.3:h:lexmark:b2442 |
| lexmark | b2546 firmware | cpe:2.3:o:lexmark:b2546_firmware |
| lexmark | b2546 | cpe:2.3:h:lexmark:b2546 |
| lexmark | b2650 firmware | cpe:2.3:o:lexmark:b2650_firmware |
| lexmark | b2650 | cpe:2.3:h:lexmark:b2650 |
| lexmark | b2865 firmware | cpe:2.3:o:lexmark:b2865_firmware |
| lexmark | b2865 | cpe:2.3:h:lexmark:b2865 |
and 188 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- lexmark b2236 firmwarebefore mslsg.081.233
- lexmark b2338 firmwarebefore msngm.081.233
- lexmark b2442 firmwarebefore msngm.081.233
- lexmark b2546 firmwarebefore msngm.081.233
- lexmark b2650 firmwarebefore msngm.081.233
- lexmark b2865 firmwarebefore msngw.081.233
- lexmark b3340 firmwarebefore mslbd.081.233
- lexmark b3442 firmwarebefore mslbd.081.233
- lexmark c2240 firmwarebefore cstzj.081.233
- lexmark c2325 firmwarebefore csnzj.081.233
- lexmark c2326 firmwarebefore cslbn.081.233
- lexmark c2425 firmwarebefore csnzj.081.233
- lexmark c2535 firmwarebefore csnzj.081.233
- lexmark c3224 firmwarebefore cslbl.081.233
- lexmark c3326 firmwarebefore cslbl.081.233
- lexmark c3426 firmwarebefore cslbl.081.233
- lexmark c4150 firmwarebefore cstat.081.233
- lexmark c6160 firmwarebefore cstpp.081.233
- lexmark c9235 firmwarebefore cstmh.081.233
- lexmark cs331 firmwarebefore cslbl.081.233
Same product
lexmark: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-23560In certain Lexmark products through 2023-01-12, SSRF can occur because of a lack of input validation.43Plan
- CVE-2021-44735Embedded web server command injection vulnerability in Lexmark devices through 2021-12-07.41Plan
- CVE-2021-44734Embedded web server input sanitization vulnerability in Lexmark devices through 2021-12-07, which can which can lead to remote code executio41Plan
Published before and after this one in the same product
- ← EarlierCVE-2021-44738Jan 20, 2022 · Buffer overflow vulnerability has been identified in Lexmark devices through 2021-12-07 in postscript interpreter.40Plan
- ← EarlierCVE-2021-44737Jan 20, 2022 · PJL directory traversal vulnerability in Lexmark devices through 2021-12-07 that can be leveraged to overwrite internal configuration files.35Monitor
- ← EarlierCVE-2022-29850Aug 25, 2022 · Various Lexmark products through 2022-04-27 allow an attacker who has already compromised an affected Lexmark device to maintain persistence32Monitor
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
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:92 | 2023-01-24 |
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.
- Published
- First PoCsame day
- TodayNov 5, 2026+1382 d
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 researchersFinders, 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
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-307 · Improper Restriction of Excessive Authentication AttemptsCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-primary
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)
- Dictionary-based Password AttackCAPEC-16likelihood: Medium · High
- Password Brute ForcingCAPEC-49likelihood: Medium · High
- Use of Known Domain CredentialsCAPEC-560likelihood: High · High
- Password SprayingCAPEC-565likelihood: High · High
- Credential StuffingCAPEC-600likelihood: High · High
- Use of Known Kerberos CredentialsCAPEC-652likelihood: Medium · High
- Use of Known Operating System CredentialsCAPEC-653likelihood: High · High
Change log
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.