Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.3amended

Products.isurlinportal has possible open redirect when using more than 2 forward slashes

CVE-2026-28413GHSA-43gx-6gv6-3jcp

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (products-isurlinportal 4.0.0, 3.1.0, 2.1.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI products-isurlinportal

    Affected
    >= 4.0.0a1, <= 4.0.0a1>= 3.0.0, < 3.1.0< 2.1.0< 2.1.0>= 3.0.0, < 3.1.0
    Fixed in
    3.1.0, 4.0.0, 2.1.0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
  • CVE-2026-28413: 0.26% estimated exploitation activity in the next 30 days; percentile 17.46 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact A url /login?camefrom=////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. Plone 6.2: upgrade to Products.isurlinportal 4.0.0. Plone 6.1: upgrade to Products.isurlinportal 3.1.0. Plone 6.0: upgrade to Products.isurlinportal 2.1.0. Older Plone versions don't have security support anymore. 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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-43gx-6gv6-3jcp

  2. Revision 1 · created ·

    Published from osv record GHSA-43gx-6gv6-3jcp

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-28413

Advisory: Products.isurlinportal has possible open redirect when using more than 2 forward slashes
IDs: CVE-2026-28413, GHSA-43gx-6gv6-3jcp
Record: https://patchnext.com/advisories/cve-2026-28413 (revision 2, source checked 26 Oct 2026, 13:44 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: products-isurlinportal 4.0.0, 3.1.0, 2.1.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI products-isurlinportal: affected >= 4.0.0a1, <= 4.0.0a1; >= 3.0.0, < 3.1.0; < 2.1.0; < 2.1.0; >= 3.0.0, < 3.1.0; fixed in 3.1.0, 4.0.0, 2.1.0

## Suggested inspection (read-only)
- `python -m pip show products-isurlinportal`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on products-isurlinportal.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-43gx-6gv6-3jcp (OSV record GHSA-43gx-6gv6-3jcp lists affected ranges: PyPI products-isurlinportal >=4.0.0a1 =3.0.0 =0 <2.1.0 (fixed))
- Verified: https://github.com/advisories/GHSA-43gx-6gv6-3jcp (GitHub-reviewed advisory GHSA-43gx-6gv6-3jcp lists affected ranges: PyPI products-isurlinportal >=4.0.0a1 =3.0.0 =0 =0 =3.0.0 <3.1.0)

Commands are suggestions: review each one before running it.

Loading voting…