CVE-2017-5524: Plone Sandbox Protection Bypass

plone Updated 02 Oct 2025

Summary

23/03/2017
Yes i
Moderate
4.3

CVE-2017-5524: 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. Affects plone across 2 version ranges.

< 4.3.12 >= 5.0a1, < 5.0.7

Fixed in 4.3.12 or 5.0.7, 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

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, editing, and publishing. Plone versions 4.x through 4.3.11 and 5.x through 5.0.6 are affected by a vulnerability that allows remote attackers to bypass a sandbox protection mechanism and obtain sensitive information. This vulnerability arises due to improper handling of the Python string format method.

Vulnerability Detail

The vulnerability in Plone allows attackers to bypass the sandbox protection mechanism and gain access to sensitive information. By leveraging the Python string format method, an attacker can manipulate the input in a way that leads to the disclosure of sensitive data. This could include user credentials, database information, or other confidential data stored within the Plone application. The impact of this vulnerability depends on the specific data that can be accessed and the privileges of the compromised user.

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.3.12 4.3.12
    pip install --upgrade "plone==4.3.12"
  • >= 5.0a1, < 5.0.7 5.0.7
    pip install --upgrade "plone==5.0.7"

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 necessary to apply the provided fix by upgrading to a patched version of Plone.

Conclusion

The Plone content management system is susceptible to a sandbox protection bypass vulnerability, allowing attackers to obtain sensitive information. To mitigate this vulnerability, users should upgrade their Plone installations to versions 4.3.12 or 5.0.7, which include the necessary fixes. It is also important to review and update any custom code or third-party plugins that may be affected. For additional support and guidance, please contact DevNack.com.

See every vulnerability recorded for plone →

Share this vulnerability

FAQ

The vulnerability allows attackers to bypass sandbox protection and access sensitive information stored within the Plone application. The impact depends on the specific data that can be accessed and the privileges of the compromised user.

You can use the Vulert playground at Vulert Scanner to check if your Plone installation is affected by this vulnerability. Simply provide your Pipfile.lock file, and Vulert will analyze it for any open-source vulnerabilities, including this one.

At the time of this report, there are no known public exploits specifically targeting this vulnerability. However, it is crucial to apply the fix promptly to mitigate any potential risks.

No, the recommended mitigation is to upgrade to a fixed version of Plone. Applying the provided fix ensures that the vulnerability is properly addressed and eliminates the risk of exploitation.

For further support and assistance in vulnerability remediation, you can reach out to info@devnack.com. Our team of experts will be happy to assist you in securing your Plone installation.

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.3.12 4.3.12
    pip install --upgrade "plone==4.3.12"
  • >= 5.0a1, < 5.0.7 5.0.7
    pip install --upgrade "plone==5.0.7"

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