CVE-2017-1000483: Plone - Accessing Private Content via str.format in Through-the-Web Templates and Scripts

plone Updated 02 Oct 2025

Summary

13/05/2022
Yes i
High
6.5

CVE-2017-1000483: Plone Unauthorized Access Vulnerability. Affects plone across 2 version ranges.

>= 2.5, < 4.3.16 >= 5.0, < 5.1.0

Fixed in 4.3.16 or 5.1.0, 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 robust and flexible platform for creating and managing websites, intranets, and web applications. Plone is written in Python and has a large community of developers and users. This vulnerability affects Plone versions 2.5 to 5.1rc1.

Vulnerability Detail

The vulnerability allows an attacker to access private content through the use of the str.format method in through-the-web templates and scripts. This vulnerability was initially addressed with a hotfix, but this specific part of the fix is relevant for Plone versions 4 and 5. The str.format method was introduced in Python 2.6, so it is only applicable to Plone versions 4 and 5. The impact of this vulnerability is unauthorized access to private content, which can lead to exposure of sensitive information.

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.

  • >= 2.5, < 4.3.16 4.3.16
    pip install --upgrade "plone==4.3.16"
  • >= 5.0, < 5.1.0 5.1.0
    pip install --upgrade "plone==5.1.0"

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 specific workaround mentioned for this vulnerability.

Conclusion

The vulnerability in Plone allows unauthorized access to private content, potentially exposing sensitive information. It is crucial to upgrade to the fixed versions of Plone to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for plone →

Share this vulnerability

FAQ

The impact of this vulnerability is unauthorized access to private content, which can lead to exposure of sensitive information.

Plone versions 2.5 to 5.1rc1 are affected by this vulnerability.

No specific workaround is mentioned for this vulnerability.

To fix this vulnerability, it is recommended to upgrade to a fixed version of Plone. For Plone 4, upgrade to version 4.3.16 or later. For Plone 5, upgrade to version 5.1.0 or later.

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.

  • >= 2.5, < 4.3.16 4.3.16
    pip install --upgrade "plone==4.3.16"
  • >= 5.0, < 5.1.0 5.1.0
    pip install --upgrade "plone==5.1.0"

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