CVE-2015-7317
First published: Mon Sep 21 2015(Updated: )
An incorrect security declaration would allow any authenticated user to edit kupu settings--the wysiwyg editor for old versions of Plone. Versions affected are all versions Plone 3 through 4.2. Upstream hotfix: <a href="https://plone.org/security/20150910/">https://plone.org/security/20150910/</a> CVE request: <a href="http://seclists.org/oss-sec/2015/q3/588">http://seclists.org/oss-sec/2015/q3/588</a>
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Kupu Project Kupu | <=1.4.16 | |
| 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 | =3.3.6 | |
| 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.0.7 | |
| Plone CMS | =4.0.8 | |
| Plone CMS | =4.0.9 | |
| Plone CMS | =4.0.10 | |
| Plone CMS | =4.1 | |
| Plone CMS | =4.1.1 | |
| Plone CMS | =4.1.2 | |
| Plone CMS | =4.1.3 | |
| Plone CMS | =4.1.4 | |
| Plone CMS | =4.1.5 | |
| Plone CMS | =4.1.6 | |
| 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.2.6 | |
| Plone CMS | =4.2.7 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2015-7317?
The severity of CVE-2015-7317 is categorized as high due to the ability for any authenticated user to edit critical settings.
How do I fix CVE-2015-7317?
To fix CVE-2015-7317, apply the upstream hotfix provided by Plone for affected versions.
Which versions are affected by CVE-2015-7317?
CVE-2015-7317 affects all versions of Plone from 3 through 4.2, including Kupu versions up to 1.4.16.
Can unauthenticated users exploit CVE-2015-7317?
No, only authenticated users can exploit CVE-2015-7317 to make unauthorized changes.
What is the impact of CVE-2015-7317 on Plone installations?
The impact of CVE-2015-7317 allows users to modify editor settings which could lead to further security vulnerabilities.
- agent/type
- agent/first-publish-date
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/weakness
- agent/severity
- agent/references
- agent/author
- agent/description
- agent/event
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2015-7317
- agent/trending
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/kupu project
- canonical/kupu project kupu
- version/kupu project kupu/1.4.16
- vendor/plone
- canonical/plone cms
- version/plone cms/3.3
- version/plone cms/3.3.1
- version/plone cms/3.3.2
- version/plone cms/3.3.3
- version/plone cms/3.3.4
- version/plone cms/3.3.5
- version/plone cms/3.3.6
- version/plone cms/4.0
- version/plone cms/4.0.1
- version/plone cms/4.0.2
- version/plone cms/4.0.3
- version/plone cms/4.0.4
- version/plone cms/4.0.5
- version/plone cms/4.0.6.1
- version/plone cms/4.0.7
- version/plone cms/4.0.8
- version/plone cms/4.0.9
- version/plone cms/4.0.10
- version/plone cms/4.1
- version/plone cms/4.1.1
- version/plone cms/4.1.2
- version/plone cms/4.1.3
- version/plone cms/4.1.4
- version/plone cms/4.1.5
- version/plone cms/4.1.6
- version/plone cms/4.2
- version/plone cms/4.2.1
- version/plone cms/4.2.2
- version/plone cms/4.2.3
- version/plone cms/4.2.4
- version/plone cms/4.2.5
- version/plone cms/4.2.6
- version/plone cms/4.2.7