plone@4.1a3 vulnerabilities
The Plone Content Management System
-
latest version
6.0.13
-
first published
16 years ago
-
latest version published
3 months ago
-
licenses detected
- [4.0rc1,)
Direct Vulnerabilities
Known vulnerabilities in the plone package. This does not include vulnerabilities belonging to this package’s dependencies.
Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.Vulnerability | Vulnerable Version |
---|---|
Plone is an user friendly and extensible Content Management System running on top of Python and Zope. Affected versions of this package are vulnerable to Information Exposure due to incorrect access control. An attacker can view and list all files hosted on the website by sending a crafted request. How to fix Information Exposure? There is no fixed version for |
[0,)
|
Plone is an user friendly and extensible Content Management System running on top of Python and Zope. Affected versions of this package are vulnerable to Cross-site Scripting (XSS) when an attacker manages to put a compromised version of the How to fix Cross-site Scripting (XSS)? Upgrade |
[,5.0)
|
Plone is an user friendly and extensible Content Management System running on top of Python and Zope. Affected versions of this package are vulnerable to Cross-site Scripting (XSS). There is 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. How to fix Cross-site Scripting (XSS)? Upgrade |
[,5.2.5)
|
Plone is an user friendly and extensible Content Management System running on top of Python and Zope. Affected versions of this package are vulnerable to XML External Entity (XXE) Injection via a feature that is protected by an unapplied permission of How to fix XML External Entity (XXE) Injection? Upgrade |
[,5.2.3)
|
Plone is an user friendly and extensible Content Management System running on top of Python and Zope. Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the tracebacks feature (only available to the Manager role). How to fix Server-side Request Forgery (SSRF)? Upgrade |
[,5.2.3)
|
Plone is an user friendly and extensible Content Management System running on top of Python and Zope. Affected versions of this package are vulnerable to XML External Entity (XXE) Injection via a feature that is explicitly only available to the Manager role. How to fix XML External Entity (XXE) Injection? Upgrade |
[,5.2.3)
|
Plone is an user friendly and extensible Content Management System running on top of Python and Zope. Affected versions of this package are vulnerable to SQL Injection in DTML or in connection objects allows users to perform unwanted SQL queries. How to fix SQL Injection? Upgrade |
[0,5.2.2)
|
Plone is a user friendly and extensible Content Management System running on top of Python and Zope. Affected versions of this package are vulnerable to Cross-site Scripting (XSS). A user with Editor or Contributor permissions can create a Folder and put JavaScript in the title. How to fix Cross-site Scripting (XSS)? Upgrade |
[0,5.2.2)
|
Plone is an user friendly and extensible Content Management System running on top of Python and Zope. Affected versions of this package are vulnerable to Privilege Escalation. Allows users to PUT (overwrite) some content without needing write permission. How to fix Privilege Escalation? Upgrade |
[0,5.2.2)
|
Plone is an user friendly and extensible Content Management System running on top of Python and Zope. Affected versions of this package are vulnerable to Cross-site Scripting (XSS). An open redirect on the login form (and possibly other places) 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. This is due to the fact that the How to fix Cross-site Scripting (XSS)? Upgrade |
[0,5.2.2)
|
plone is a user friendly and extensible Content Management System running on top of Python and Zope. Affected versions of this package are vulnerable to Arbitrary Code Execution. How to fix Arbitrary Code Execution? Upgrade |
[,4.2.3)
|
plone is a Content Management System running on top of Python and Zope. Affected versions of this package are vulnerable to Sandbox escape. Accessing private content via str.format in through-the-web templates and scripts. How to fix Sandbox Escape? Upgrade |
[4.0,4.3.16)
[5,5.1.0)
|
plone is a Content Management System running on top of Python and Zope. Affected versions of this package are vulnerable to Cross-site Scripting (XSS). An attacker may set javascript in the How to fix Cross-site Scripting (XSS)? Upgrade |
[,4.3.16)
[5,5.1.0)
|
plone is a Content Management System running on top of Python and Zope. Affected versions of this package are vulnerable to Open Redirect. By linking to a specific url in Plone with a parameter, an attacker could send the user to his own website. How to fix Open Redirect? Upgrade |
[2.5,5.1)
|
plone is a Content Management System running on top of Python and Zope. Affected versions of this package are vulnerable to Open Redirect and reflected Cross-site Scripting (XSS) attacks. An attacker might persuade a user to click on a specially crafted link, and get him redirect to a malicious site. How to fix Open Redirect? Upgrade |
[,4.3.16)
[5,5.1.0)
|
Affected versions of this package are vulnerable to Cross-site Request Forgery (CSRF). Multiple cross-site request forgery (CSRF) vulnerabilities in Zope Management Interface 4.3.7 and earlier, and Plone before 5.x. |
[,4.3.7)
[5.0a1,5.0)
|
Affected versions of this package are vulnerable to Sandbox Bypass. Plone 4.x through 4.3.11 and 5.x through 5.0.6 allow remote attackers to bypass a sandbox protection mechanism and obtain sensitive information by leveraging the Python string format method. |
[4,5.1a2]
|
Affected versions of this package are vulnerable to Cross-site Scripting (XSS). |
[,5.1a2]
|
Affected versions of this package are vulnerable to Cross-site Scripting (XSS) attacks due to unescaped user input in a page template. |
[4,5.1a1]
|
Affected versions of this package are vulnerable to Cross-site Scripting (XSS) attacks. z3c.form will currently accept data from GET requests when the form is supposed to be POST. This allows a user to inject a potential XSS attack into a form. With certain widgets in Plone admin forms, the input is expected to be safe and can cause a reflexive XSS attack. Additionally, there is potential for an attack that will trick a user into saving a persistent XSS. |
[4,5.1a1]
|
Affected versions of this package are vulnerable to Open Redirect. In multiple places, Plone blindly uses the referer header to redirect a user to the next page after a particular action. An attacker could utilize this to draw a user into a redirection attack. |
[,5.0.6]
|
Affected versions of this package are vulnerable to Cross-site Scripting (XSS) attacks. Plone's URL checking infrastructure includes a method for checking if URLs valid and located in the Plone site. By passing javascript into this specially crafted url, XSS can be achieved. |
[,5.1a1]
|
Affected versions of this package are vulnerable to Information Exposure. Plone 3.3 through 5.1a1 allows remote attackers to obtain information about the ID of sensitive content via unspecified vectors. |
[3.3,5.1a1]
|
Affected versions of this package are vulnerable to Access Restriction Bypass. Dexterity content is missing security declarations for WebDAV requests. This only affects Dexterity objects. |
[4.0,5.1a1]
|
Affected versions of this package are vulnerable to Access Restriction Bypass. An incorrect security declaration would allow any authenticated user to edit kupu settings--the wysiwyg editor for old versions of Plone. Versions affected are all versions Plone 3 through 4.2. |
[3.3,4.2.7]
|
Affected versions of this package are vulnerable to Unauthorized user creation. A vulnerability that allows remote attackers to add a new member to a Plone site when registration is enabled, without acknowledgment of site administrator was found. Versions affected are Plone 3.x, 4.1.x, 4.2.x, <4.3.7, <5.0rc1. |
[,4.3.7)
|
Affected versions of this package are vulnerable to Cross-site Scripting (XSS) attacks. Plone's URL checking infrastructure includes a method for checking if URLs valid and located in the Plone site. By passing HTML into this specially crafted url, XSS can be achieved. Versions affected are Plone 3.x, 4.1.x, 4.2.x, <4.3.7, <5.0rc1. |
[,4.3.7)
|
Products/CMFPlone/FactoryTool.py in Plone 3.3 through 4.3.2 allows remote attackers to obtain the installation path via vectors related to a file object for unspecified documentation which is initialized in class scope. |
[3.3,4.3.2]
|
Products/CMFPlone/CatalogTool.py in Plone 3.3 through 4.3.2 allows remote administrators to bypass restrictions and obtain sensitive information via an unspecified search API. |
[3.3,4.3.2]
|
traverser.py in Plone 2.1 through 4.1, 4.2.x through 4.2.5, and 4.3.x through 4.3.1 allows remote attackers with administrator privileges to cause a Denial of Service (infinite loop and resource consumption) via unspecified vectors related to "retrieving information for certain resources." |
[,4.2.5)
[4.3,4.3.1)
|
Multiple unspecified vulnerabilities in (1) dataitems.py, (2) get.py, and (3) traverseName.py in Plone 2.1 through 4.1, 4.2.x through 4.2.5, and 4.3.x through 4.3.1 allow remote authenticated users with administrator access to a subtree to access nodes above the subtree via unknown vectors. |
[,4.2.5)
[4.3,4.3.1)
|
Multiple Cross-site Scripting (XSS) vulnerabilities in (1) spamProtect.py, (2) pts.py, and (3) request.py in Plone 2.1 through 4.1, 4.2.x through 4.2.5, and 4.3.x through 4.3.1 allow remote attackers to inject arbitrary web script or HTML via unspecified vectors. |
[,4.2.5)
[4.3,4.3.1)
|
zip.py in Plone 2.1 through 4.1, 4.2.x through 4.2.5, and 4.3.x through 4.3.1 does not properly enforce access restrictions when including content in a zip archive, which allows remote attackers to obtain sensitive information by reading a generated archive. |
[,4.2.5)
[4.3,4.3.1)
|
sendto.py in Plone 2.1 through 4.1, 4.2.x through 4.2.5, and 4.3.x through 4.3.1 allows remote authenticated users to spoof emails via unspecified vectors. |
[,4.2.5)
[4.3,4.3.1)
|
typeswidget.py in Plone 2.1 through 4.1, 4.2.x through 4.2.5, and 4.3.x through 4.3.1 does not properly enforce the immutable setting on unspecified content edit forms, which allows remote attackers to hide fields on the forms via a crafted URL. |
[,4.2.5)
[4.3,4.3.1)
|
The WYSIWYG component (wysiwyg.py) in Plone 2.1 through 4.1, 4.2.x through 4.2.5, and 4.3.x through 4.3.1 allows remote attackers to obtain sensitive information via a crafted URL, which reveals the installation path in an error message. |
[,4.2.5)
[4.3,4.3.1)
|
Multiple open redirect vulnerabilities in (1) marmoset_patch.py, (2) publish.py, and (3) principiaredirect.py in Plone 2.1 through 4.1, 4.2.x through 4.2.5, and 4.3.x through 4.3.1 allow remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via unspecified vectors. |
[,4.2.5)
[4.3,4.3.1)
|
The object manager implementation (objectmanager.py) in Plone 2.1 through 4.1, 4.2.x through 4.2.5, and 4.3.x through 4.3.1 does not properly restrict access to internal methods, which allows remote attackers to obtain sensitive information via a crafted request. |
[,4.2.5)
[4.3,4.3.1)
|
member_portrait.py in Plone 2.1 through 4.1, 4.2.x through 4.2.5, and 4.3.x through 4.3.1 allows remote authenticated users to modify or delete portraits of other users via unspecified vectors. |
[,4.2.5)
[4.3,4.3.1)
|
mail_password.py in Plone 2.1 through 4.1, 4.2.x through 4.2.5, and 4.3.x through 4.3.1 allows remote authenticated users to bypass the prohibition on password changes via the forgotten password email functionality. |
[,4.2.5)
[4.3,4.3.1)
|
(1) cb_decode.py and (2) linkintegrity.py in Plone 2.1 through 4.1, 4.2.x through 4.2.5, and 4.3.x through 4.3.1 allow remote authenticated users to cause a Denial of Service (resource consumption) via a large zip archive, which is expanded (decompressed). |
[,4.2.5)
[4.3,4.3.1)
|
The sandbox whitelisting function (allowmodule.py) in Plone before 4.2.3 and 4.3 before beta 1 allows remote authenticated users with certain privileges to bypass the Python sandbox restriction and execute arbitrary Python code via vectors related to importing. |
[,4.2.3)
[4.3a1,4.3b1)
|
python_scripts.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via a crafted URL, related to createObject. |
[,4.2.3)
[4.3a1,4.3b1)
|
Cross-site Scripting (XSS) vulnerability in kssdevel.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors. |
[,4.2.3)
[4.3a1,4.3b1)
|
gtbn.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote authenticated users with certain permissions to bypass the Python sandbox and execute arbitrary Python code via unspecified vectors. |
[,4.2.3)
[4.3a1,4.3b1)
|
uid_catalog.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to obtain metadata about hidden objects via a crafted URL. |
[,4.2.3)
[4.3a1,4.3b1)
|
Cross-site Scripting (XSS) vulnerability in python_scripts.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors, related to "{u,}translate." |
[,4.2.3)
[4.3a1,4.3b1)
|
python_scripts.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via a crafted URL, related to "go_back." |
[,4.2.3)
[4.3a1,4.3b1)
|
membership_tool.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to enumerate user account names via a crafted URL. |
[,4.2.3)
[4.3a1,4.3b1)
|
queryCatalog.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to bypass caching and cause a Denial of Service via a crafted request to a collection. |
[,4.2.3)
[4.3a1,4.3b1)
|
python_scripts.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to cause a Denial of Service (memory consumption) via a large value, related to formatColumns. |
[,4.2.3)
[4.3a1,4.3b1)
|
The batch id change script (renameObjectsByPaths.py) in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to change the titles of content items by leveraging a valid CSRF token in a crafted request. |
[,4.2.3)
[4.3a1,4.3b1)
|
at_download.py in Plone before 4.2.3 and 4.3.0 before beta 1 allows remote attackers to read arbitrary BLOBs (Files and Images) stored on custom content types via a crafted URL. How to fix Arbitrary BLOB Read? Upgrade |
[,4.2.3)
[4.3a1,4.3b1)
|
Cross-site Scripting (XSS) vulnerability in safe_html.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote authenticated users with permissions to edit content to inject arbitrary web script or HTML via unspecified vectors. How to fix Cross-site Scripting (XSS)? Upgrade |
[,4.2.3)
[4.3.a1,4.3b1)
|
ftp.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to read hidden folder contents via unspecified vectors. How to fix Information Exposure? Upgrade |
[,4.2.3)
[4.3a1,4.3b1)
|
Cross-site Scripting (XSS) vulnerability in widget_traversal.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors. How to fix Cross-site Scripting (XSS)? Upgrade |
[,4.2.3)
[4.3.a1,4.3b1)
|
atat.py in Plone before 4.2.3 and 4.3.0 before beta 1 allows remote attackers to read private data structures via a request for a view without a name. How to fix Information Exposure? Upgrade |
[,4.2.3)
[4.3.a1,4.3b1)
|
python_scripts.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to cause a Denial of Service (infinite loop) via an RSS feed request for a folder the user does not have permission to access. How to fix Denial of Service (DoS)? Upgrade |
[,4.2.3)
[4.3a1,4.3b1)
|
The error pages in Plone before 4.2.3 and 4.3 before beta 1 allow remote attackers to obtain random numbers and derive the PRNG state for password resets via unspecified vectors. NOTE: this identifier was SPLIT per ADT2 due to different vulnerability types. CVE-2012-6661 was assigned for the PRNG reseeding issue in Zope. |
[,4.2.3)
[4.3a1,4.3b1)
|
z3c.form, as used in Plone before 4.2.3 and 4.3 before beta 1, allows remote attackers to obtain the default form field values by leveraging knowledge of the form location and the element id. |
[,4.2.3)
[4.3a1,4.3b1)
|
Plone 4.1.3 and earlier computes hash values for form parameters without restricting the ability to trigger hash collisions predictably, which allows remote attackers to cause a Denial of Service (CPU consumption) by sending many crafted parameters. |
[,4.1.3]
|
Cross-site Scripting (XSS) vulnerability in Plone 4.1 and earlier allows remote attackers to inject arbitrary web script or HTML via a crafted URL. |
[,4.2)
|
plone.app.users in Plone 4.0 and 4.1 allows remote authenticated users to modify the properties of arbitrary accounts via unspecified vectors, as exploited in the wild in June 2011. |
[4,4.2)
|
Unspecified vulnerability in Plone 2.5 through 4.0, as used in Conga, luci, and possibly other products, allows remote attackers to obtain administrative access, read or create arbitrary content, and change the site skin via unknown vectors. |
[2.5,4.1)
|