CVE-2013-4191: Plone - Improper Access Restrictions in zip.py

plone Updated 02 Oct 2025

Summary

17/05/2022

Disclosed on

CVE-2013-4191

CVE

Yes i

Fix available

Moderate

Severity

4.8

CVSS Score

CVE-2013-4191: Plone is vulnerable to Information Exposure when generating zip archives. Affects plone across 3 version ranges.

>= 2.1, < 4.1.1 >= 4.2, < 4.2.6 >= 4.3, < 4.3.2

Fixed in 4.1.1, 4.2.6 or 4.3.2, 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 Browse

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.

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

Vulnerability Detail

The vulnerability (CVE-2013-4191) exists in the zip.py module of Plone versions 2.1 through 4.1, 4.2.x through 4.2.5, and 4.3.x through 4.3.1. It arises from a failure to enforce access restrictions when including content in a zip archive. This flaw allows remote attackers to gain unauthorized access to sensitive information by reading a generated archive. By exploiting this vulnerability, an attacker can potentially obtain confidential data stored within the Plone instance, leading to data breaches and privacy violations.

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.1, < 4.1.1 4.1.1
```
pip install --upgrade "plone==4.1.1"
```
>= 4.2, < 4.2.6 4.2.6
```
pip install --upgrade "plone==4.2.6"
```
>= 4.3, < 4.3.2 4.3.2
```
pip install --upgrade "plone==4.3.2"
```

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 recommended fix by upgrading to a patched version of Plone.

Conclusion

The vulnerability (CVE-2013-4191) in Plone's zip.py module allows remote attackers to obtain sensitive information by bypassing access restrictions when including content in a zip archive. To mitigate this issue, it is crucial to upgrade to a fixed version of Plone (4.1.1, 4.2.6, or 4.3.2). For further assistance and support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for plone →

FAQ

What is Plone?

Plone is an open-source content management system used for building websites and web applications.

What versions of Plone are affected by this vulnerability?

Plone versions 2.1 through 4.1, 4.2.x through 4.2.5, and 4.3.x through 4.3.1 are affected.

How can this vulnerability be exploited?

Remote attackers can exploit this vulnerability by reading a generated archive and obtaining sensitive information.

What are the potential consequences of this vulnerability?

The vulnerability can lead to unauthorized access to confidential data stored within the Plone instance, resulting in data breaches and privacy violations.