Skip to content
Fencer Intel
high 8.8

CVE-2016-5383 json

The web UI in Red Hat CloudForms 4.1 allows remote authenticated users to execute arbitrary code via vectors involving "Lack of field filte…

published 2016-08-26 10 y ago modified 2026-06-17 4 mo ago also EUVD-2016-6333

cvss
8.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.6%
EPSS 2.6% chance of exploitation in 30 days, percentile 85%
public exploits
0
none known

Summary

The web UI in Red Hat CloudForms 4.1 allows remote authenticated users to execute arbitrary code via vectors involving "Lack of field filters."

Patch / fix

  • cfme cloudforms managementengine 5.6 5.6.1.2-1.el7cf
  • cfme-gemset cloudforms managementengine 5.6 5.6.1.2-1.el7cf
  • google-config cloudforms managementengine 5.6 2.0.0-1.el7cf
  • cfme-appliance cloudforms managementengine 5.6 5.6.1.2-1.el7cf
  • google-compute-engine cloudforms managementengine 5.6 2.0.0-1.el7cf

red hat advisories RHSA-2016:1634

Vendor advisories

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

red hat product security vex CVE-2016-5383 updated cvss 7.7

CloudForms: Lack of field filters on user input

  • Red Hat CloudForms Management Engine 5.6 cfme 5.6.1.2-1.el7cf, cfme-gemset 5.6.1.2-1.el7cf, google-config 2.0.0-1.el7cf, cfme-appliance 5.6.1.2-1.el7cf, google-compute-engine 2.0.0-1.el7cf
    fixed: vendor fix RHSA-2016:1634

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

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

CVSS scores

assigned by version score vector
NVD 3.0 8.8 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 6.5 AV:N/AC:L/Au:S/C:P/I:P/A:P

Classification

Weakness

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.