Plone CMS vulnerabilitiesRanked by how likely they are to be used.
Plone CMS is made by Plone. We track 5 published vulnerabilities in it, across 6 versions. None of them is on the list of flaws known to be exploited today. If you run Plone CMS, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Plone CMS vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Plone CMS's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Plone CMS flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 2.9%CVE-2008-1393Critical
Plone CMS 3.0.5, and probably other 3.x versions, places a base64 encoded form of the username and password in the __ac cookie for the admin account, which makes it easier for remote attackers to obtain...
- 1.4%CVE-2008-1394High
Plone CMS before 3 places a base64 encoded form of the username and password in the __ac cookie for all user accounts, which makes it easier for remote attackers to obtain access by sniffing the network.
- 1.3%CVE-2008-1395High
Plone CMS does not record users' authentication states, and implements the logout feature solely on the client side, which makes it easier for context-dependent attackers to reuse a logged-out session.
- 1.1%CVE-2008-1396Medium
Plone CMS 3.x uses invariant data (a client username and a server secret) when calculating an HMAC-SHA1 value for an authentication cookie, which makes it easier for remote attackers to gain permanent access to an...
- 0.6%CVE-2008-0164Medium
Multiple cross-site request forgery (CSRF) vulnerabilities in Plone CMS 3.0.5 and 3.0.6 allow remote attackers to (1) add arbitrary accounts via the join_form page and (2) change the privileges of arbitrary groups...
Running Plone CMS? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Plone CMS 3.0.5, and probably other 3.x versions, places a base64 encoded form of the username and password in the __ac cookie for the admin account, which makes it easier for remote attackers to obtain administrative privileges by sniffing the network.
- Matched to
- Plone CMS on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 5 published vulnerabilities listed under the name Plone CMS, across 6 versions.
None of Plone CMS's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Plone CMS. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.