CVE-2017-1000481: Medium severity plone cms vulnerability

Published Jan 3, 2018
·
Updated

When you visit a page where you need to login, Plone 2.5-5.1rc1 sends you to the login form with a 'camefrom' parameter set to the previous url. After you login, you get redirected to the page you tried to view before. An attacker might try to abuse this by letting you click on a specially crafted link. You would login, and get redirected to the site of the attacker, letting you think that you are still on the original Plone site. Or some javascript of the attacker could be executed. Most of these types of attacks are already blocked by Plone, using the isURLInPortal check to make sure we only redirect to a page on the same Plone site. But a few more ways of tricking Plone into accepting a malicious link were discovered, and fixed with this hotfix.

Affected Software

72 affected componentsFixes available
pip/Plone>=5<5.1.0
5.1.0
pip/Plone>=2.5<4.3.16
4.3.16
pip/Products.CMFPlone>=5.1a1<5.1.0
5.1.0
pip/Products.CMFPlone>=5.0.0<5.0.10
5.0.10
pip/Products.CMFPlone<4.3.17
4.3.17
Plone plone=2.5.5
Plone plone=3.3
Plone plone=3.3.1
Plone plone=3.3.2
Plone plone=3.3.3
Plone plone=3.3.4
Plone plone=3.3.5
Plone plone=3.3.6
Plone plone=4.0
Plone plone=4.0.1
Plone plone=4.0.2
Plone plone=4.0.3
Plone plone=4.0.4
Plone plone=4.0.5
Plone plone=4.0.7
Plone plone=4.0.8
Plone plone=4.0.9
Plone plone=4.0.10
Plone plone=4.1
Plone plone=4.1.1
Plone plone=4.1.2
Plone plone=4.1.3
Plone plone=4.1.4
Plone plone=4.1.5
Plone plone=4.1.6
Plone plone=4.2
Plone plone=4.2.1
Plone plone=4.2.2
Plone plone=4.2.3
Plone plone=4.2.4
Plone plone=4.2.5
Plone plone=4.2.6
Plone plone=4.2.7
Plone plone=4.3
Plone plone=4.3.1
Plone plone=4.3.2
Plone plone=4.3.3
Plone plone=4.3.4
Plone plone=4.3.5
Plone plone=4.3.6
Plone plone=4.3.7
Plone plone=4.3.8
Plone plone=4.3.9
Plone plone=4.3.10
Plone plone=4.3.11
Plone plone=4.3.12
Plone plone=4.3.14
Plone plone=4.3.15
Plone plone=5.0
Plone plone=5.0-rc1
Plone plone=5.0-rc2
Plone plone=5.0-rc3
Plone plone=5.0.1
Plone plone=5.0.2
Plone plone=5.0.3
Plone plone=5.0.4
Plone plone=5.0.5
Plone plone=5.0.6
Plone plone=5.0.7
Plone plone=5.0.8
Plone plone=5.0.9
Plone plone=5.1-a1
Plone plone=5.1-a2
Plone plone=5.1-b2
Plone plone=5.1-b3
Plone plone=5.1-b4
Plone plone=5.1-rc1

Event History

Jan 3, 2018
CVE Published
via MITRE·06:00 PM
Data Sourced
via MITRE·06:00 PM
Description
May 14, 2022
Advisory Published
03:49 AM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2017-1000481?

The severity of CVE-2017-1000481 is classified as medium due to the potential for an open redirect attack.

2

How do I fix CVE-2017-1000481?

To fix CVE-2017-1000481, upgrade to Plone version 5.1.0, 5.0.10, or 4.3.17.

3

Which versions of Plone are affected by CVE-2017-1000481?

CVE-2017-1000481 affects Plone versions 2.5.5 to 5.1-rc1, including various versions in between.

4

What type of attack does CVE-2017-1000481 allow?

CVE-2017-1000481 allows attackers to perform open redirect attacks through manipulation of the 'came_from' parameter.

5

Is authentication compromised in CVE-2017-1000481?

Authentication is not compromised in CVE-2017-1000481, but it can lead users to unintended malicious sites after login.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203