CVE-2013-4193: Plone - Unspecified Content Edit Form Field Hiding

plone Updated 02 Oct 2025

Summary

11/03/2014
Yes i
High
5.9

CVE-2013-4193: typeswidget.py in Plone 2.1 through 4.1, 4.2.x through 4.2.5, and 4.3.x through 4.3.1 does not properly enforce the immutable setting on unspecified content edit forms, which allows remote attackers to hide fields on the... 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

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 (CMS) built on top of the Zope application server. It provides a user-friendly interface for managing websites, intranets, and collaborative workspaces. Plone allows users to create, edit, and publish content through various forms and widgets. However, versions 2.1 through 4.1, 4.2.x through 4.2.5, and 4.3.x through 4.3.1 of Plone suffer from a vulnerability that allows remote attackers to hide fields on unspecified content edit forms.

Vulnerability Detail

The vulnerability in Plone arises from the improper enforcement of the immutable setting on unspecified content edit forms. By crafting a malicious URL, remote attackers can manipulate the forms and hide specific fields. This can lead to various security issues, such as unauthorized access, data manipulation, or bypassing intended restrictions. The vulnerability affects multiple versions of Plone, making it crucial for users to address this issue promptly.

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

No specific workaround has been provided for this vulnerability.

Conclusion

The vulnerability in Plone versions 2.1 through 4.1, 4.2.x through 4.2.5, and 4.3.x through 4.3.1 allows remote attackers to hide fields on unspecified content edit forms. To mitigate this issue, users should upgrade their Plone installations to the fixed versions (4.1.1, 4.2.6, or 4.3.2). It is recommended to test the upgraded installation thoroughly before deploying it to production environments. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for plone →

Share this vulnerability

FAQ

The vulnerability allows remote attackers to hide fields on unspecified content edit forms, which can lead to unauthorized access, data manipulation, or bypassing intended restrictions.

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

You can use the Vulert Playground at Vulert Scanner to check if your Plone installation is affected by this vulnerability. Simply enter your Pipfile.lock and it will provide real-time alerts for open-source vulnerabilities.

There are no known exploits for this vulnerability at the time of this report. However, it is crucial to address the issue promptly to mitigate potential risks.

You can find more information about this vulnerability in the Plone advisory PYSEC-2014-57 at https://github.com/pypa/advisory-database/blob/main/vulns/plone/PYSEC-2014-57.yaml.

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.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 →

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