CVE-2012-5500: CSRF
A security flaw was found in the way Plone, a user friendly and powerful content management system, performed permissions checks for change titles of content items action. A remote attacker (anonymous user) could submit a specially-crafted HTTP POST request that, when processed, would allow them in an unauthorized way to change titles of content items.
References: [1] http://plone.org/products/plone/security/advisories/20121106/16 [2] http://plone.org/products/plone/security/advisories/20121106/
Relevant upstream HotFixes: [3] http://plone.org/products/plone-hotfix/releases/20121106
From the OSS post: [4] http://www.openwall.com/lists/oss-security/2012/11/07/4
the renameObjectsByPaths.py change from upstream HotFix is relevant to this issue.
Other sources
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.
— MITRE
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2012-5500?
CVE-2012-5500 has a medium severity level due to the potential for unauthorized title changes of content items by remote attackers.
How do I fix CVE-2012-5500?
To fix CVE-2012-5500, upgrade Plone to version 4.2.3 or later.
Which versions of Plone are affected by CVE-2012-5500?
CVE-2012-5500 affects Plone versions up to and including 4.2.2 and all versions from 1.0 to 4.2.x.
What are the impacts of exploiting CVE-2012-5500?
Exploiting CVE-2012-5500 allows an unauthenticated attacker to modify titles of content items, potentially leading to confusion or misuse of the content.
Is CVE-2012-5500 still a concern for users of Plone?
Yes, CVE-2012-5500 remains a concern for users running vulnerable versions of Plone, necessitating prompt updates.