Filtered by vendor Plone
Subscriptions
Filtered by product Plone
Subscriptions
Total
104 CVE
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2020-28734 | 1 Plone | 1 Plone | 2024-08-04 | 8.8 High |
| Plone before 5.2.3 allows XXE attacks via a feature that is explicitly only available to the Manager role. | ||||
| CVE-2020-7938 | 1 Plone | 1 Plone | 2024-08-04 | 8.8 High |
| plone.restapi in Plone 5.2.0 through 5.2.1 allows users with a certain privilege level to escalate their privileges up to the highest level. | ||||
| CVE-2020-7940 | 1 Plone | 1 Plone | 2024-08-04 | 7.5 High |
| Missing password strength checks on some forms in Plone 4.3 through 5.2.0 allow users to set weak passwords, leading to easier cracking. | ||||
| CVE-2020-7941 | 1 Plone | 1 Plone | 2024-08-04 | 9.8 Critical |
| A privilege escalation issue in plone.app.contenttypes in Plone 4.3 through 5.2.1 allows users to PUT (overwrite) some content without needing write permission. | ||||
| CVE-2020-7939 | 1 Plone | 1 Plone | 2024-08-04 | 8.8 High |
| SQL Injection in DTML or in connection objects in Plone 4.0 through 5.2.1 allows users to perform unwanted SQL queries. (This is a problem in Zope.) | ||||
| CVE-2020-7936 | 1 Plone | 1 Plone | 2024-08-04 | 6.1 Medium |
| An open redirect on the login form (and possibly other places) in Plone 4.0 through 5.2.1 allows an attacker to craft a link to a Plone Site that, when followed, and possibly after login, will redirect to an attacker's site. | ||||
| CVE-2020-7937 | 1 Plone | 1 Plone | 2024-08-04 | 5.4 Medium |
| An XSS issue in the title field in Plone 5.0 through 5.2.1 allows users with a certain privilege level to insert JavaScript that will be executed when other users access the site. | ||||
| CVE-2021-35959 | 1 Plone | 1 Plone | 2024-08-04 | 5.4 Medium |
| In Plone 5.0 through 5.2.4, Editors are vulnerable to XSS in the folder contents view, if a Contributor has created a folder with a SCRIPT tag in the description field. | ||||
| CVE-2021-33926 | 1 Plone | 1 Plone | 2024-08-04 | 8.8 High |
| An issue in Plone CMS v. 5.2.4, 5.2.3, 5.2.2, 5.2.1, 5.2.0, 5.1rc2, 5.1rc1, 5.1b4, 5.1b3, 5.1b2, 5.1a2, 5.1a1, 5.1.7, 5.1.6, 5.1.5, 5.1.4, 5.1.2, 5.1.1 5.1, 5.0rc3, 5.0rc2, 5.0rc1, 5.0.9, 5.0.8, 5.0.7, 5.0.6, 5.0.5, 5.0.4, 5.0.3, 5.0.2, 5.0.10, 5.0.1, 5.0, 4.3.9, 4.3.8, 4.3.7, 4.3.6, 4.3.5, 4.3.4, 4.3.3, 4.3.20, 4 allows attacker to access sensitive information via the RSS feed protlet. | ||||
| CVE-2021-33512 | 1 Plone | 1 Plone | 2024-08-03 | 5.4 Medium |
| Plone through 5.2.4 allows stored XSS attacks (by a Contributor) by uploading an SVG or HTML document. | ||||
| CVE-2021-33509 | 1 Plone | 1 Plone | 2024-08-03 | 9.9 Critical |
| Plone through 5.2.4 allows remote authenticated managers to perform disk I/O via crafted keyword arguments to the ReStructuredText transform in a Python script. | ||||
| CVE-2021-33507 | 2 Plone, Zope | 2 Plone, Zope | 2024-08-03 | 6.1 Medium |
| Zope Products.CMFCore before 2.5.1 and Products.PluggableAuthService before 2.6.2, as used in Plone through 5.2.4 and other products, allow Reflected XSS. | ||||
| CVE-2021-33510 | 1 Plone | 1 Plone | 2024-08-03 | 4.3 Medium |
| Plone through 5.2.4 allows remote authenticated managers to conduct SSRF attacks via an event ical URL, to read one line of a file. | ||||
| CVE-2021-33511 | 1 Plone | 1 Plone | 2024-08-03 | 7.5 High |
| Plone though 5.2.4 allows SSRF via the lxml parser. This affects Diazo themes, Dexterity TTW schemas, and modeleditors in plone.app.theming, plone.app.dexterity, and plone.supermodel. | ||||
| CVE-2021-33513 | 1 Plone | 1 Plone | 2024-08-03 | 5.4 Medium |
| Plone through 5.2.4 allows XSS via the inline_diff methods in Products.CMFDiffTool. | ||||
| CVE-2021-33508 | 1 Plone | 1 Plone | 2024-08-03 | 5.4 Medium |
| Plone through 5.2.4 allows XSS via a full name that is mishandled during rendering of the ownership tab of a content item. | ||||
| CVE-2021-32633 | 2 Plone, Zope | 2 Plone, Zope | 2024-08-03 | 6.8 Medium |
| Zope is an open-source web application server. In Zope versions prior to 4.6 and 5.2, users can access untrusted modules indirectly through Python modules that are available for direct use. By default, only users with the Manager role can add or edit Zope Page Templates through the web, but sites that allow untrusted users to add/edit Zope Page Templates through the web are at risk from this vulnerability. The problem has been fixed in Zope 5.2 and 4.6. As a workaround, a site administrator can restrict adding/editing Zope Page Templates through the web using the standard Zope user/role permission mechanisms. Untrusted users should not be assigned the Zope Manager role and adding/editing Zope Page Templates through the web should be restricted to trusted users only. | ||||
| CVE-2021-29002 | 1 Plone | 1 Plone | 2024-08-03 | 5.4 Medium |
| A stored cross-site scripting (XSS) vulnerability in Plone CMS 5.2.3 exists in site-controlpanel via the "form.widgets.site_title" parameter. | ||||
| CVE-2021-21336 | 2 Plone, Zope | 2 Plone, Products.pluggableauthservice | 2024-08-03 | 6.5 Medium |
| Products.PluggableAuthService is a pluggable Zope authentication and authorization framework. In Products.PluggableAuthService before version 2.6.0 there is an information disclosure vulnerability - everyone can list the names of roles defined in the ZODB Role Manager plugin if the site uses this plugin. The problem has been fixed in version 2.6.0. Depending on how you have installed Products.PluggableAuthService, you should change the buildout version pin to 2.6.0 and re-run the buildout, or if you used pip simply do `pip install "Products.PluggableAuthService>=2.6.0"`. | ||||
| CVE-2021-3313 | 1 Plone | 1 Plone | 2024-08-03 | 5.4 Medium |
| Plone CMS until version 5.2.4 has a stored Cross-Site Scripting (XSS) vulnerability in the user fullname property and the file upload functionality. The user's input data is not properly encoded when being echoed back to the user. This data can be interpreted as executable code by the browser and allows an attacker to execute JavaScript in the context of the victim's browser if the victim opens a vulnerable page containing an XSS payload. | ||||