Skip to content
Fencer Intel
medium 5.3

CVE-2012-5500 json

Plone contains Cross-site Request Forgery

published 2014-11-03 12 y ago modified 2026-06-16 4 mo ago also GHSA-2q75-f7cp-w86q , PYSEC-2014-42 , EUVD-2014-0060

cvss
5.3
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
1.1%
EPSS 1.1% chance of exploitation in 30 days, percentile 65%
public exploits
0
none known

Summary

The batch id change script (renameObjectsByPaths.py) in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to change the titles of content items by leveraging a valid CSRF token in a crafted request.

Patch / fix

  • pypi plone 4.2.3, 4.3b1
  • conga RHEL 5 CLUSTER 0.12.2-81.el5
  • luci RHEL 5 CLUSTER 0.12.2-81.el5
  • ricci RHEL 5 CLUSTER 0.12.2-81.el5

red hat advisories RHSA-2014:1194

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2012-5500 updated cvss 2.6

(Plone): Anonymous users can batch change titles of content items

  • Red Hat Enterprise Linux 5 conga
    affected: no fix available
  • Red Hat Enterprise Linux Clustering (v. 5 server) luci 0.12.2-81.el5, conga 0.12.2-81.el5, ricci 0.12.2-81.el5
    fixed: vendor fix RHSA-2014:1194

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.10% chance of exploitation in the next 30 days, higher than 65% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
pypi plone
<4.2.3
>=4.3a1, <4.3b1
>=4.3a0, <4.3b1
4.2.3
4.3b1

Classification

Weakness
  • CWE-352 Cross-Site Request Forgery

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.