CVE-2017-1000481

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in, but needs a user to act. Limited direct impact.

Exploit odds

0.7% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2018-01-03 18:29 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 00:59 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.7% in the next 30 days (EPSS).
• Severity: 6.1 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2018-01-03 18:29 UTC

Last modified

2026-06-17 00:59 UTC

Exploit probability

0.7% · EPSS, next 30 days

Weakness

CWE-601

Record status

Modified

Affected

• Plone 2.5.5
• Plone 3.3
• Plone 3.3.1
• Plone 3.3.2
• Plone 3.3.3
• Plone 3.3.4
• Plone 3.3.5
• Plone 3.3.6

Attack profile CVSS 3.0 · 6.1

Attack vector

Network

Complexity

Low

Privileges needed

None

User interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2017-1000481.md and follow it. Check whether this project is affected by CVE-2017-1000481. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge