← Back
CVE-2026-28413

Open Redirect in products-isurlinportal (CVE-2026-28413)

Summary

vulnerability in products-isurlinportal (CVE-2026-28413). Risk of unauthorized operations or information disclosure. Exploitable via ``Products.isurlinportal``. Mitigation: upgrade to `3.1.0` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-28413** has been found in products-isurlinportal. Attackers can target a specific entry point like ``Products.isurlinportal`` over the network to misuse the product. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade products-isurlinportal to **3.1.0** or later. If unsure, ask your IT team or search "products-isurlinportal CVE-2026-28413" on the vendor's site.
CVE-2026-28413 (products-isurlinportal) — CWE-601 / Attack vector: remote (network-reachable) / unauthenticated / no user interaction Attack surface: `Products.isurlinportal` Patched: `3.1.0` — apply immediately Workaround: There are no known workarounds. Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs. Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-601) exists in products-isurlinportal. Attackers reach the vulnerable code path via ``Products.isurlinportal`` without authentication.
📍 Affected scope
products-isurlinportal — . Attack surface: `Products.isurlinportal`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **3.1.0**.
🛡️ Workaround
Workaround: There are no known workarounds.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'products-isurlinportal' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'products-isurlinportal' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `products-isurlinportal` を grep し、稼働しているサービス・バージョンを把握する。

  2. 5
    Apply temporary workaround mitigate
    There are no known workarounds.

    パッチが適用されるまでの応急処置として、There are no known workarounds. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 6
    Apply patch patch
    Upgrade products-isurlinportal to 3.1.0

    ステージング環境で 3.1.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  4. 7
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

PyPI products-isurlinportal
[{"type":"ECOSYSTEM","events":[{"introduced":"3.0.0"},{"fixed":"3.1.0"}]}]
pip Products.isurlinportal
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.1.0"}]}]
pip products-isurlinportal
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.0"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →