CVE-2012-5493: Plone Remote Code Execution

plone Updated 02 Oct 2025

Summary

17/05/2022
Yes i
Moderate
9.9

CVE-2012-5493: Plone Sandbox Bypass. 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 ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

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 secure and scalable web applications.

Vulnerability Detail

The vulnerability (CVE-2012-5493) affects Plone versions before 4.2.3 and 4.3 beta 1. It allows remote authenticated users with certain permissions to bypass the Python sandbox and execute arbitrary Python code. The specific vectors through which this can be exploited are not disclosed in the vulnerability details. However, it is important to note that this vulnerability can lead to unauthorized code execution, potentially compromising the integrity and security of the Plone instance.

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.3 4.2.3
    pip install --upgrade "plone==4.2.3"
  • >= 4.3a0, < 4.3b1 4.3b1
    pip 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

No specific workaround is mentioned in the vulnerability details. However, as a general best practice, it is recommended to follow the fix provided above and upgrade to the latest secure version of Plone.

Conclusion

The vulnerability (CVE-2012-5493) in Plone allows remote authenticated users to execute arbitrary Python code by bypassing the Python sandbox. To mitigate this vulnerability, it is crucial to upgrade to Plone version 4.2.3 or later. For further assistance and support in vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for plone →

Share this vulnerability

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.

Plone versions before 4.2.3 and 4.3 beta 1 are affected by this vulnerability.

Remote authenticated users with certain permissions can exploit this vulnerability to bypass the Python sandbox and execute arbitrary Python code. The specific vectors through which this can be exploited are not disclosed in the vulnerability details.

This vulnerability can lead to unauthorized code execution, potentially compromising the integrity and security of the Plone instance.

To fix this vulnerability, it is recommended to upgrade to Plone version 4.2.3 or later if using a version prior to 4.3 beta 1. This involves patching the codebase to address the security flaw and prevent the bypass of the Python sandbox.

Related vulnerabilities

Recent vulnerabilities recorded for plone.

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.3 4.2.3
    pip install --upgrade "plone==4.2.3"
  • >= 4.3a0, < 4.3b1 4.3b1
    pip 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback