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
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.3.17, 5.0.10, 5.1.0, 4.3.16
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- n/a n/a
Version range not reported
- products-cmfplonePyPI
fixed in 4.3.17
- products-cmfplonePyPI
From 5.0.0 · fixed in 5.0.10
- products-cmfplonePyPI
From 5.1a1 · fixed in 5.1.0
- plonePyPI
From 2.5 · fixed in 4.3.16
- plonePyPI
From 5 · fixed in 5.1.0
- products-cmfplonePyPI
fixed in 4.3.17; From 5.0.0 · fixed in 5.0.10; From 5.1a1 · fixed in 5.1.0
- plonePyPI
From 2.5 · fixed in 4.3.16; From 5 · fixed in 5.1.0