CVE-2017-14011 json
A Cross-Site Request Forgery issue was discovered in ProMinent MultiFLEX M10a Controller web interface.
published 2017-10-17 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-5526
- cvss
- 8.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 50%
- public exploits
- 0
- none known
Summary
A Cross-Site Request Forgery issue was discovered in ProMinent MultiFLEX M10a Controller web interface. The application does not sufficiently verify requests, making it susceptible to cross-site request forgery. This may allow an attacker to execute unauthorized code, resulting in changes to the configuration of the device.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-17-285-01 updated cvss 8.8
ProMinent MultiFLEX M10a Controller
-
ProMinent MultiFLEX M10a Controller web interfaceaffected: mitigation “ProMinent has not provided mitigations for these vulnerabilities.”
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
0.64% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Affected products
- n/a ProMinent MultiFLEX M10a Controller
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
securityfocus.com
/bid/101259
vdb-entry, third-party-advisory
-
ics-cert.us-cert.gov
/advisories/ICSA-17-285-01
mitigation, third-party-advisory, us-government-resource
Sources
- CVE List CVE-2017-14011
- NVD CVE-2017-14011
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.