CVE-2021-42635 json
PrinterLogic Web Stack versions 19.1.1.13 SP9 and below use a hardcoded APP_KEY value, leading to pre-auth remote code execution.
published 2022-01-31 4 y ago modified 2026-07-09 4 mo ago also EUVD-2021-29599
- cvss
- 8.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 5.6%
- EPSS 5.6% chance of exploitation in 30 days, percentile 92%
- public exploits
- 0
- none known
Summary
PrinterLogic Web Stack versions 19.1.1.13 SP9 and below use a hardcoded APP_KEY value, leading to pre-auth remote code execution.
Patch / fix
- printerlogic web_stack 19.1.1.13
Exploit prediction
5.57% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- yahooinc.com https://www.yahooinc.com/paranoids/paranoids-vulnerability-research-printerlogic-issues-security-alert/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-798 Use of Hard-coded Credentials
References
-
yahooinc.com
/paranoids/paranoids-vulnerability-research-printerlogic-issues-security-alert/
exploit, press/media-coverage, third-party-advisory
-
printerlogic.com
/security-bulletin/
vendor-advisory
-
securityweek.com
/printerlogic-patches-code-execution-flaws-printer-management-suite
press/media-coverage, third-party-advisory
-
securityaffairs.co
/wordpress/127194/security/printerlogic-printer-management-suite-flaws.html
third-party-advisory
-
portswigger.net
/daily-swig/printerlogic-vendor-addresses-triple-rce-threat-against-all-connected-endpoints
press/media-coverage, third-party-advisory
-
thecyberthrone.in
/2022/01/26/printerlogic-%F0%9F%96%A8-fixes-critical-vulnerabilities-in-its-suite/?utm_source=rss&utm_medium=r
press/media-coverage, third-party-advisory
Sources
- CVE List CVE-2021-42635
- NVD CVE-2021-42635
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.