CVE-2012-5487
HighSummary
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.
Risk Assessment
The organization may be exposed to the execution of malicious code by authenticated users, potentially leading to serious security breaches and data loss.
Recommendation
It is recommended to update Plone to version 4.2.3 or later to mitigate this vulnerability and review user permissions to restrict access to the whitelisting function.
Other vulnerabilities in Plone
See all- CVE-2015-7318High
Plone versions 3.3.0 through 3.3.6 allow remote attackers to inject headers into HTTP responses.
- CVE-2016-4041High
Plone versions 4.0 through 5.1a1 lack security declarations for Dexterity content-related WebDAV requests, allowing remote attackers to gain WebDAV access via unspecified vectors.
- CVE-2012-5493High
In gtbn.py in Plone before 4.2.3 and 4.3 before beta 1, remote authenticated users with certain permissions can bypass the Python sandbox and execute arbitrary Python code via unspecified vectors.
- CVE-2024-23054Critical
An issue in the Plone Docker Official Image 5.2.13 (5221) where a package listed in ++plone++static/components does not exist in the public npm package index, potentially allowing remote code execution.
- CVE-2024-23055Medium
An issue in the official Plone Docker image version 5.2.13 (5221) allows remote code execution due to improper validation of HOST headers.
Original NVD description (English source)
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.