CVE-2019-7267 in the critical feed json
Linear eMerge 50P/5000P devices allow Cookie Path Traversal.
published 2019-07-02 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-16811
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 21.5%
- EPSS 21.5% chance of exploitation in 30 days, percentile 97%
- public exploits
- 0
- none known
Summary
Linear eMerge 50P/5000P devices allow Cookie Path Traversal.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-20-184-01 updated cvss 9.8
Nortek Linear eMerge 50P/5000P
-
Nortek Linear eMerge 50P/5000P <= 4.6.07affected: mitigation “Nortek has released v32-09a. For more information please contact Nortek customer support.” nortekcontrol.com
From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf
Exploit prediction
21.45% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- packetstormsecurity.com http://packetstormsecurity.com/files/155250/Linear-eMerge50P-5000P-4.6.07-Remote-Code-Execution.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
packetstormsecurity.com
/files/155250/Linear-eMerge50P-5000P-4.6.07-Remote-Code-Execution.html
exploit, third-party-advisory, vdb-entry
-
applied-risk.com
/labs/advisories
broken-link, not-applicable, third-party-advisory
-
applied-risk.com
/resources/ar-2019-006
third-party-advisory
-
us-cert.gov
/ics/advisories/icsa-20-184-01
third-party-advisory, us-government-resource
Sources
- CVE List CVE-2019-7267
- NVD CVE-2019-7267
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.