CVE-2012-5487: Plone Sandbox Whitelisting Bypass
Summary
CVE-2012-5487: 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 Pyth... Affects plone across 2 version ranges.
< 4.2.3
>= 4.3a0, < 4.3b1
Fixed in 4.2.3 or 4.3b1, depending on the release line you run. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
Plone is an open-source content management system built on top of the Zope application server. It provides a user-friendly interface for managing websites and supports various features such as content creation, collaboration, and workflow management. Plone is widely used in both small and large organizations for building robust and secure web applications.
However, prior to version 4.2.3 and 4.3 beta 1, Plone was vulnerable to a sandbox whitelisting bypass. The sandbox whitelisting function, known as allowmodule.py, allowed remote authenticated users with certain privileges to bypass the Python sandbox restriction and execute arbitrary Python code. This vulnerability could lead to unauthorized access, data manipulation, and potential system compromise.
Vulnerability Detail
The sandbox whitelisting function in Plone had a flaw that allowed authenticated users to bypass the Python sandbox restriction. By exploiting this vulnerability, an attacker with the necessary privileges could execute arbitrary Python code. The issue was related to the importing of modules, which could be manipulated to execute malicious code within the Plone environment. This could result in unauthorized actions, data leakage, or even complete compromise of the affected Plone instance.
The vulnerability was assigned CVE-2012-5487 and was disclosed on September 30, 2014. It was addressed in Plone versions 4.2.3 and 4.3 beta 1.
How To Fix
Latest published version: 6.2.2 as of 23 Oct 2026
pip install --upgrade "plone==6.2.2"Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.
If you can't move to the latest
The minimum fixed version depends on the release line you run.
-
< 4.2.34.2.3pip install --upgrade "plone==4.2.3" -
>= 4.3a0, < 4.3b14.3b1pip install --upgrade "plone==4.3b1"
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
There is no known workaround for this vulnerability. It is essential to apply the official patches or upgrade to the fixed versions of Plone to address the issue.
Conclusion
The sandbox whitelisting bypass vulnerability in Plone could allow authenticated users to execute arbitrary Python code and compromise the affected Plone instance. To mitigate this risk, it is essential to update the Plone installation to at least version 4.2.3 or 4.3 beta 1. Additionally, it is recommended to follow best practices for securing the Plone environment and regularly apply security patches.
For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for plone →
FAQ
Plone is an open-source content management system built on top of the Zope application server. It provides a user-friendly interface for managing websites and supports various features such as content creation, collaboration, and workflow management.
Sandbox whitelisting is a security mechanism that restricts the execution of certain operations or code within a controlled environment. In the case of Plone, the sandbox whitelisting function was designed to prevent the execution of arbitrary Python code by limiting the imported modules.
The vulnerability allows authenticated users with certain privileges to bypass the Python sandbox restriction in Plone. This means that they can execute arbitrary Python code, potentially leading to unauthorized actions, data manipulation, or even complete compromise of the affected Plone instance.
Yes, the vulnerability has been fixed in Plone versions 4.2.3 and 4.3 beta 1. It is recommended to update the Plone installation to one of these versions or a later release to mitigate the risk.
If you are using an older version of Plone, it is crucial to upgrade to at least version 4.2.3 or 4.3 beta 1. These versions include the necessary patches to address the sandbox whitelisting bypass vulnerability.
References
Related vulnerabilities
Recent vulnerabilities recorded for plone.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
