First published: Wed Jun 26 2013(Updated: )
A security flaw was found in the way Plone, a user friendly and powerful content management system, enforced immutable setting on certain content edit forms. A remote attacker could use this flaw to provide a specially-crafted URL that would (in a non-persistent way) hide certain fields from these content edit forms, possibly leading to scenario such altered forms to be erroneously accepted by authenticated Plone user as valid.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
pip/plone | >=4.3<4.3.2 | 4.3.2 |
pip/plone | >=4.2<4.2.6 | 4.2.6 |
pip/plone | >=2.1<=4.1 | 4.1.1 |
Plone CMS | =2.1 | |
Plone CMS | =2.1.1 | |
Plone CMS | =2.1.2 | |
Plone CMS | =2.1.3 | |
Plone CMS | =2.1.4 | |
Plone CMS | =2.5 | |
Plone CMS | =2.5.1 | |
Plone CMS | =2.5.2 | |
Plone CMS | =2.5.3 | |
Plone CMS | =2.5.4 | |
Plone CMS | =2.5.5 | |
Plone CMS | =3.0 | |
Plone CMS | =3.0.1 | |
Plone CMS | =3.0.2 | |
Plone CMS | =3.0.3 | |
Plone CMS | =3.0.4 | |
Plone CMS | =3.0.5 | |
Plone CMS | =3.0.6 | |
Plone CMS | =3.1 | |
Plone CMS | =3.1.1 | |
Plone CMS | =3.1.2 | |
Plone CMS | =3.1.3 | |
Plone CMS | =3.1.4 | |
Plone CMS | =3.1.5.1 | |
Plone CMS | =3.1.6 | |
Plone CMS | =3.1.7 | |
Plone CMS | =3.2 | |
Plone CMS | =3.2.1 | |
Plone CMS | =3.2.2 | |
Plone CMS | =3.2.3 | |
Plone CMS | =3.3 | |
Plone CMS | =3.3.1 | |
Plone CMS | =3.3.2 | |
Plone CMS | =3.3.3 | |
Plone CMS | =3.3.4 | |
Plone CMS | =3.3.5 | |
Plone CMS | =4.0 | |
Plone CMS | =4.0.1 | |
Plone CMS | =4.0.2 | |
Plone CMS | =4.0.3 | |
Plone CMS | =4.0.4 | |
Plone CMS | =4.0.5 | |
Plone CMS | =4.0.6.1 | |
Plone CMS | =4.1 | |
Plone CMS | =4.2 | |
Plone CMS | =4.2.1 | |
Plone CMS | =4.2.2 | |
Plone CMS | =4.2.3 | |
Plone CMS | =4.2.4 | |
Plone CMS | =4.2.5 | |
Plone CMS | =4.3 | |
Plone CMS | =4.3.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2013-4193 is classified as a moderate severity vulnerability due to its potential to allow an attacker to modify form fields.
To fix CVE-2013-4193, you should upgrade to a patched version of Plone that addresses this vulnerability.
CVE-2013-4193 affects Plone versions 2.1 through 4.3.1.
Yes, CVE-2013-4193 can be exploited remotely through specially-crafted URLs.
CVE-2013-4193 does not lead to persistent data loss but could temporarily hide fields during editing.