CVE-2012-5508: Plone - PRNG State Leakage in Error Pages

plone Updated 02 Oct 2025

Summary

03/11/2014
Yes i
Moderate
5.3

CVE-2012-5508: The error pages in Plone before 4.2.3 and 4.3 before beta 1 allow remote attackers to obtain random numbers and derive the PRNG state for password resets via unspecified vectors. Affects plone across 2 version ranges.

< 4.2.3 >= 4.3a0, < 4.3b1

Fixed in 4.2.3 or 4.3b1, 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 Your last release was probably never penetration tested 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 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 secure web applications.

Vulnerability Detail

The error pages in Plone versions before 4.2.3 and 4.3 before beta 1 suffer from a vulnerability that allows remote attackers to obtain random numbers and derive the PRNG (Pseudorandom Number Generator) state for password resets. This vulnerability can be exploited by attackers to predict or manipulate the random numbers used in password reset operations, potentially leading to unauthorized access to user accounts. The exact vectors through which this leakage occurs are unspecified.

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.2.3 4.2.3
    pip install --upgrade "plone==4.2.3"
  • >= 4.3a0, < 4.3b1 4.3b1
    pip install --upgrade "plone==4.3b1"

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. It is advised to follow the recommended fix by upgrading to the patched versions of Plone.

Conclusion

The error pages in Plone versions before 4.2.3 and 4.3 before beta 1 contain a vulnerability that allows leakage of the PRNG state, potentially leading to unauthorized access to user accounts. To mitigate this vulnerability, it is crucial to upgrade to the recommended patched versions of Plone. For further support and assistance in vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for plone →

Share this vulnerability

FAQ

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

The vulnerability allows remote attackers to obtain random numbers and derive the PRNG state for password resets, potentially leading to unauthorized access to user accounts.

To fix this vulnerability, upgrade to Plone version 4.2.3 or later if using a version prior to 4.2.3. For versions 4.3a0 and earlier, upgrade to version 4.3b1 or later.

No specific workarounds have been provided for this vulnerability. It is recommended to upgrade to the patched versions of Plone.

For more information about this vulnerability, you can refer to the official Plone advisory: [link to advisory].

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.2.3 4.2.3
    pip install --upgrade "plone==4.2.3"
  • >= 4.3a0, < 4.3b1 4.3b1
    pip install --upgrade "plone==4.3b1"

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