When you visit a page where you need to login, Plone 2.5-5.1rc1 sends you to the login form with a 'came_from' 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.
This vulnerability carries a MEDIUM severity rating with a CVSS v3.1 score of 6.1, indicating it can be exploited remotely over the network with relatively low complexity though user interaction is required and does not require pre-existing privileges . The vulnerability impacts limited data confidentiality, limited integrity, for affected systems. Impacting 1 product from plone organizations running these solutions should prioritize assessment and patching.
First disclosed in 2018, this vulnerability was reported during a period defined by widespread IoT adoption challenges, mobile security concerns, and the emergence of advanced persistent threat (APT) techniques. Contemporary mitigation strategies focused on secure development practices and third-party component vetting.
2018-01-03T18:29:00.400
2024-11-21T03:04:49.823
Modified
CVSSv3.0: 6.1 (MEDIUM)
AV:N/AC:M/Au:N/C:P/I:P/A:N
8.6
4.9
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Application | plone | plone | 2.5.5 | Yes |
| Application | plone | plone | 3.3 | Yes |
| Application | plone | plone | 3.3.1 | Yes |
| Application | plone | plone | 3.3.2 | Yes |
| Application | plone | plone | 3.3.3 | Yes |
| Application | plone | plone | 3.3.4 | Yes |
| Application | plone | plone | 3.3.5 | Yes |
| Application | plone | plone | 3.3.6 | Yes |
| Application | plone | plone | 4.0 | Yes |
| Application | plone | plone | 4.0.1 | Yes |
| Application | plone | plone | 4.0.2 | Yes |
| Application | plone | plone | 4.0.3 | Yes |
| Application | plone | plone | 4.0.4 | Yes |
| Application | plone | plone | 4.0.5 | Yes |
| Application | plone | plone | 4.0.7 | Yes |
| Application | plone | plone | 4.0.8 | Yes |
| Application | plone | plone | 4.0.9 | Yes |
| Application | plone | plone | 4.0.10 | Yes |
| Application | plone | plone | 4.1 | Yes |
| Application | plone | plone | 4.1.1 | Yes |
| Application | plone | plone | 4.1.2 | Yes |
| Application | plone | plone | 4.1.3 | Yes |
| Application | plone | plone | 4.1.4 | Yes |
| Application | plone | plone | 4.1.5 | Yes |
| Application | plone | plone | 4.1.6 | Yes |
| Application | plone | plone | 4.2 | Yes |
| Application | plone | plone | 4.2.1 | Yes |
| Application | plone | plone | 4.2.2 | Yes |
| Application | plone | plone | 4.2.3 | Yes |
| Application | plone | plone | 4.2.4 | Yes |
| Application | plone | plone | 4.2.5 | Yes |
| Application | plone | plone | 4.2.6 | Yes |
| Application | plone | plone | 4.2.7 | Yes |
| Application | plone | plone | 4.3 | Yes |
| Application | plone | plone | 4.3.1 | Yes |
| Application | plone | plone | 4.3.2 | Yes |
| Application | plone | plone | 4.3.3 | Yes |
| Application | plone | plone | 4.3.4 | Yes |
| Application | plone | plone | 4.3.5 | Yes |
| Application | plone | plone | 4.3.6 | Yes |
| Application | plone | plone | 4.3.7 | Yes |
| Application | plone | plone | 4.3.8 | Yes |
| Application | plone | plone | 4.3.9 | Yes |
| Application | plone | plone | 4.3.10 | Yes |
| Application | plone | plone | 4.3.11 | Yes |
| Application | plone | plone | 4.3.12 | Yes |
| Application | plone | plone | 4.3.14 | Yes |
| Application | plone | plone | 4.3.15 | Yes |
| Application | plone | plone | 5.0 | Yes |
| Application | plone | plone | 5.0 | Yes |
| Application | plone | plone | 5.0 | Yes |
| Application | plone | plone | 5.0 | Yes |
| Application | plone | plone | 5.0.1 | Yes |
| Application | plone | plone | 5.0.2 | Yes |
| Application | plone | plone | 5.0.3 | Yes |
| Application | plone | plone | 5.0.4 | Yes |
| Application | plone | plone | 5.0.5 | Yes |
| Application | plone | plone | 5.0.6 | Yes |
| Application | plone | plone | 5.0.7 | Yes |
| Application | plone | plone | 5.0.8 | Yes |
| Application | plone | plone | 5.0.9 | Yes |
| Application | plone | plone | 5.1 | Yes |
| Application | plone | plone | 5.1 | Yes |
| Application | plone | plone | 5.1 | Yes |
| Application | plone | plone | 5.1 | Yes |
| Application | plone | plone | 5.1 | Yes |
| Application | plone | plone | 5.1 | Yes |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For plone's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.