Skip to content
Fencer Intel
critical 9.8

CVE-2019-7274 in the critical feed json

Optergy Proton/Enterprise devices allow Authenticated File Upload with Code Execution as root.

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

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

Summary

Optergy Proton/Enterprise devices allow Authenticated File Upload with Code Execution as root.

Is CVE-2019-7274 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-157-01 updated cvss 3.1

Optergy Proton Enterprise Building Management System

  • Optergy Proton/Enterprise <= 2.3.0a
    affected: mitigation “Update Optergy server to Version 2.4.5 (or later) to remediate the issues described in this advisory (Proton and Optergy Enterprise).”

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

Exploit prediction

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

Exploits and checks

  • EDB-47636 Optergy 2.3.0a - Remote Code Execution webapps, 2019-11-12
  • packetstormsecurity.com http://packetstormsecurity.com/files/155269/Optergy-2.3.0a-Remote-Root.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 10.0 AV:N/AC:L/Au:N/C:C/I:C/A:C

Classification

Weakness
  • CWE-434 Unrestricted Upload of File with Dangerous Type

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.