First published: Fri Feb 17 2023(Updated: )
An issue in Plone CMS allows attacker to access sensitive information via the RSS feed protlet.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
pip/Plone | >=4.3<5.2.5 | 5.2.5 |
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 | =4.3.10 | |
Plone CMS | =4.3.11 | |
Plone CMS | =4.3.12 | |
Plone CMS | =4.3.14 | |
Plone CMS | =4.3.15 | |
Plone CMS | =4.3.17 | |
Plone CMS | =4.3.18 | |
Plone CMS | =4.3.19 | |
Plone CMS | =4.3.20 | |
Plone CMS | =5.0 | |
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 | |
Plone CMS | =5.0.5 | |
Plone CMS | =5.0.6 | |
Plone CMS | =5.0.7 | |
Plone CMS | =5.0.8 | |
Plone CMS | =5.0.9 | |
Plone CMS | =5.0.10 | |
Plone CMS | =5.1-alpha2 | |
Plone CMS | =5.1.1 | |
Plone CMS | =5.1.2 | |
Plone CMS | =5.1.4 | |
Plone CMS | =5.1.5 | |
Plone CMS | =5.1.6 | |
Plone CMS | =5.1.7 | |
Plone CMS | =5.1a1-alpha1 | |
Plone CMS | =5.1a2-beta4 | |
Plone CMS | =5.1b2-beta3 | |
Plone CMS | =5.1b3-beta2 | |
Plone CMS | =5.1b4-rc2 | |
Plone CMS | =5.1rc1-rc1 | |
Plone CMS | =5.1rc2 | |
Plone CMS | =5.2.0 | |
Plone CMS | =5.2.1 | |
Plone CMS | =5.2.2 | |
Plone CMS | =5.2.3 | |
Plone CMS | =5.2.4 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
You can determine vulnerability by checking if your Plone CMS version is 5.2.4 or earlier and comparing it against the official security release notes.