First published: Fri Feb 24 2017(Updated: )
Plone 3.3 through 5.1a1 allows remote attackers to obtain information about the ID of sensitive content via unspecified vectors.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
pip/Plone | >=3.3<4.3.10 | 4.3.10 |
pip/Plone | >=5.0<5.0.5 | 5.0.5 |
Plone CMS | =3.3 | |
Plone CMS | =3.3.1 | |
Plone CMS | =3.3.2 | |
Plone CMS | =3.3.3 | |
Plone CMS | =3.3.4 | |
Plone CMS | =3.3.5 | |
Plone CMS | =3.3.6 | |
Plone CMS | =4.0 | |
Plone CMS | =4.0.1 | |
Plone CMS | =4.0.2 | |
Plone CMS | =4.0.3 | |
Plone CMS | =4.0.4 | |
Plone CMS | =4.0.5 | |
Plone CMS | =4.0.7 | |
Plone CMS | =4.0.8 | |
Plone CMS | =4.0.9 | |
Plone CMS | =4.0.10 | |
Plone CMS | =4.1 | |
Plone CMS | =4.1.1 | |
Plone CMS | =4.1.2 | |
Plone CMS | =4.1.3 | |
Plone CMS | =4.1.4 | |
Plone CMS | =4.1.5 | |
Plone CMS | =4.1.6 | |
Plone CMS | =4.2 | |
Plone CMS | =4.2.1 | |
Plone CMS | =4.2.2 | |
Plone CMS | =4.2.3 | |
Plone CMS | =4.2.4 | |
Plone CMS | =4.2.5 | |
Plone CMS | =4.2.6 | |
Plone CMS | =4.2.7 | |
Plone CMS | =4.3 | |
Plone CMS | =4.3.1 | |
Plone CMS | =4.3.2 | |
Plone CMS | =4.3.3 | |
Plone CMS | =4.3.4 | |
Plone CMS | =4.3.5 | |
Plone CMS | =4.3.6 | |
Plone CMS | =4.3.7 | |
Plone CMS | =4.3.8 | |
Plone CMS | =4.3.9 | |
Plone CMS | =5.0 | |
Plone CMS | =5.0-a1 | |
Plone CMS | =5.0-rc1 | |
Plone CMS | =5.0-rc2 | |
Plone CMS | =5.0-rc3 | |
Plone CMS | =5.0.1 | |
Plone CMS | =5.0.2 | |
Plone CMS | =5.0.3 | |
Plone CMS | =5.0.4 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-4042 is considered to have a moderate severity level as it allows attackers to obtain sensitive content IDs.
To fix CVE-2016-4042, upgrade your Plone installation to version 4.3.10 or 5.0.5.
CVE-2016-4042 affects Plone versions from 3.3 up to, but not including, 4.3.10, and 5.x versions up to, but not including, 5.0.5.
Yes, CVE-2016-4042 can potentially expose sensitive content IDs to unauthorized users.
The impact of CVE-2016-4042 is that it may lead to information disclosure regarding the structure and content of the site.