CVE-2013-4192: Plone Email Spoofing Vulnerability

plone Updated 02 Oct 2025

Summary

11/03/2014
Yes i
High
6.5

CVE-2013-4192: sendto.py in Plone 2.1 through 4.1, 4.2.x through 4.2.5, and 4.3.x through 4.3.1 allows remote authenticated users to spoof emails via unspecified vectors. 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 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 offers features such as content editing, workflow management, and user authentication. However, versions 2.1 through 4.1, 4.2.x through 4.2.5, and 4.3.x through 4.3.1 of Plone are vulnerable to an email spoofing attack.

Vulnerability Detail

The vulnerability in Plone allows remote authenticated users to spoof emails through unspecified vectors. This means that an attacker with valid credentials can send emails that appear to come from a different sender. By impersonating a trusted source, the attacker may trick recipients into taking malicious actions or disclosing sensitive information. The exact method of exploitation is not disclosed in the vulnerability details.

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 is provided in the vulnerability details. Users are advised to apply the fix by upgrading to the patched versions of Plone.

Conclusion

The Plone Email Spoofing Vulnerability (CVE-2013-4192) allows authenticated users to send spoofed emails, potentially leading to various malicious activities. Users of Plone should upgrade to the fixed versions (4.1.1, 4.2.6, or 4.3.2) to mitigate this vulnerability. For further support on vulnerability remediation, you can contact 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 robust and flexible platform for creating and managing websites, intranets, and web applications.

Email spoofing is the forgery of an email header to make it appear as if it came from someone or somewhere other than the actual source. In this vulnerability, authenticated users can send emails that appear to come from a different sender.

Email spoofing can be used for various malicious purposes, such as phishing attacks, spreading malware, or tricking recipients into revealing sensitive information.

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, and Vulert will analyze it for any open-source vulnerabilities.

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