Skip to content
Fencer Intel
critical 9.0

CVE-2019-7671 json

Prima Systems FlexAir, Versions 2.3.38 and prior.

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

cvss
9.0
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
8.1%
EPSS 8.1% chance of exploitation in 30 days, percentile 94%
public exploits
1
Exploit-DB

Summary

Prima Systems FlexAir, Versions 2.3.38 and prior. Parameters sent to scripts are not properly sanitized before being returned to the user, which may allow an attacker to execute arbitrary code in a user’s browser session in context of an affected site.

Is CVE-2019-7671 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-19-211-02 updated cvss 5.4

Prima Systems FlexAir

  • Prima Systems Prima FlexAir <= 2.3.38
    affected: mitigation “Prima Systems has released Version 2.5.12 to fix these issues.”

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-47633)

Exploit prediction

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

Exploits and checks

  • EDB-47633 Prima Access Control 2.3.35 - 'HwName' Persistent Cross-Site Scripting webapps, 2019-11-12
  • packetstormsecurity.com http://packetstormsecurity.com/files/155274/Prima-Access-Control-2.3.35-Cross-Site-Scripting.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 9.0 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
NVD 2.0 3.5 AV:N/AC:M/Au:S/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.