Skip to content
Fencer Intel
medium 6.1

CVE-2019-7255 json

Linear eMerge E3-Series devices allow XSS.

published 7y ago modified 4mo ago also EUVD-2019-16799

cvss
6.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
55.7%
EPSS 55.7% chance of exploitation in 30 days, percentile 99%
public exploits
1
Exploit-DB, plus a Nuclei check

Summary

Linear eMerge E3-Series devices allow XSS.

Is CVE-2019-7255 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-24-065-01 updated cvss 6.1

Nice Linear eMerge E3-Series

  • Nice Linear eMerge E3-Series <=1.00-06
    affected: mitigation “Nice/Nortek encourages users to upgrade to the latest firmware to mitigate the risk of these vulnerabilities. Please see Nice's E3-Bulletin for more information.” linear-solutions.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

Timeline

  1. Published
  2. First public exploit (EDB-47623)

Exploit prediction

55.65% chance of exploitation in the next 30 days, higher than 99% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-47623 eMerge E3 1.00-06 - 'layout' Reflected Cross-Site Scripting webapps, 2019-11-12
  • Nuclei template Linear eMerge E3 - Cross-Site Scripting nuclei detection template
  • packetstormsecurity.com http://packetstormsecurity.com/files/155253/Linear-eMerge-E3-1.00-06-Cross-Site-Scripting.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

Fencer Intel 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.