products-isurlinportal
Affected
- introduced
4.0.0a1, fixed4.0.0(ecosystem)
Fixed versions
4.0.0
Fix
- Fixed version
4.0.0pip install --upgrade products-isurlinportal==4.0.0
Advisory
Also known as: CVE-2026-28413, PYSEC-2026-112
Products.isurlinportal has possible open redirect when using more than 2 forward slashes
Impact
A url /login?came_from=////evil.example may redirect to an external website after login.
Standard Plone is not affected, but if you have customised the login, for example with add-ons, you might be affected. You can try the url to check if you are affected or not.
Patches
The problem has been patched in Products.isurlinportal.
Products.isurlinportal 4.0.0.Products.isurlinportal 3.1.0.Products.isurlinportal 2.1.0.Workarounds
There are no known workarounds.
Background
When you are anonymous and land on a page that requires a login, Plone sends you to the login form. After successful login, Plone redirects you back to the page you came from. Various other forms and pages have a similar system.
This could get abused by an attacker to trick Plone into redirecting to a different website. Plone checks the page that would be redirected to. It is only accepted if it is within the Plone site domain or part of a different trusted domain.
The main check for this is in the Products.isurlinportal package. A lot of potentially malicious urls are already safely rejected, but here a loop hole was found.
This was discovered during a penetration test by the CERT-EU Team.
Medium Basis: The source's own band: MODERATE
4.0.0a1, fixed 4.0.0 (ecosystem)4.0.0
4.0.0pip install --upgrade products-isurlinportal==4.0.03.0.0, fixed 3.1.0 (ecosystem)3.1.0
3.1.0pip install --upgrade products-isurlinportal==3.1.00, fixed 2.1.0 (ecosystem)2.1.0
2.1.0pip install --upgrade products-isurlinportal==2.1.00, fixed 2.1.0 (ecosystem)2.1.0
2.1.0pip install --upgrade products-isurlinportal==2.1.03.0.0, fixed 3.1.0 (ecosystem)3.1.0
3.1.0pip install --upgrade products-isurlinportal==3.1.0Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0