Is CVE-2012-5500 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2012-5500 being exploited in the wild.

How severe is CVE-2012-5500?

Low severity, with a CVSS score of 3.1, published 3 November 2014.

Which products and versions are affected?

Plone before 4.2.3; 4.3 before beta 1; plone (PyPI) ECOSYSTEM:introduced=0,fixed=4.2.3,introduced=4.3a0,fixed=4.3b1.

Is there a fix for CVE-2012-5500?

Yes. plone (PyPI): upgrade to 4.3b1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2012-5500 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2012-5500?

Check whether you run Plone or plone (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2012-5500: Plone cross-site request forgery in batch rename script

CVE-2012-5500 · Severity: low · CVSS 3.1 · Published 2014-11-03

Plone is an open-source content management system used to build and manage websites. A flaw in the batch rename functionality allows remote attackers to change the titles of content items without proper authorization by exploiting a CSRF vulnerability. An attacker could alter site content, potentially damaging site integrity and user trust.

Technologies: Plone, plone (PyPI). Vendors: Plone, PyPI.

Quick answers

Is CVE-2012-5500 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2012-5500 being exploited in the wild.
How severe is CVE-2012-5500?: Low severity, with a CVSS score of 3.1, published 3 November 2014.
Which products and versions are affected?: Plone before 4.2.3; 4.3 before beta 1; plone (PyPI) ECOSYSTEM:introduced=0,fixed=4.2.3,introduced=4.3a0,fixed=4.3b1.
Is there a fix for CVE-2012-5500?: Yes. plone (PyPI): upgrade to 4.3b1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2012-5500 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2012-5500?: Check whether you run Plone or plone (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

plone (PyPI): upgrade to 4.3b1 or later
```
pip install "plone>=4.3b1"
```

Technical details

Plone before version 4.2.3 and 4.3 beta 1 contains a cross-site request forgery (CSRF) vulnerability in the batch ID change script (renameObjectsByPaths.py). The vulnerability exists because the script does not properly enforce CSRF protections on content title modification requests. An unauthenticated remote attacker can craft a malicious web page that, when visited by a logged-in administrator, will execute a request to change content titles. No special preconditions beyond admin session presence are required. The attacker can change titles of arbitrary content items, compromising site data integrity. Patches are available in Plone 4.2.3 and 4.3 beta 1 and later.

Affected products

Plone Plone before 4.2.3; 4.3 before beta 1

Identifiers

CVE-2012-5500
GHSA-2q75-f7cp-w86q
PYSEC-2014-42

Timeline

2012-11-06: disclosed
2012-11: patched: Plone 4.2.3 and 4.3 beta 1
2022-05-17: advisory: GHSA-2q75-f7cp-w86q published

References

https://access.redhat.com/errata/RHSA-2014:1194

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.