Open RedirectWeakness · CWE-601

CVE-2019-25282

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
V-SOL GPON/EPON OLT Platform v2.03 contains an open redirect vulnerability in the script that allows attackers to manipulate the 'parent' GET parameter. Attackers can craft malicious links that redirect logged-in users to arbitrary websites by exploiting improper input validation in the redirect mechanism.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

V-SOL GPON/EPON OLT Platform v2.03 contains an open redirect vulnerability where the 'parent' GET parameter is not properly validated, allowing attackers to craft malicious URLs that redirect authenticated users to arbitrary external websites by exploiting improper input validation in the redirect mechanism.

MitigationImplement strict input validation and whitelist-based redirect logic to ensure the 'parent' parameter only allows trusted internal paths, rejecting any attempts to redirect to external domains or unauthorized URLs.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm V-SOL GPON/EPON OLT Platform is running
    Access the device administrative interface and verify the product name displays as V-SOL GPON/EPON OLT Platform. Check the system information or about page for the exact model and firmware version.
    Affected if The device is running V-SOL GPON/EPON OLT Platform firmware version 2.03.
  2. Verify the firmware version
    Locate the firmware version in the device admin panel, typically under System, Maintenance, or About sections. Compare the installed version number to 2.03.
    Affected if The installed firmware version is exactly 2.03.
  3. Identify scripts accepting the 'parent' parameter
    Review the web application's URL patterns and identify endpoints that accept a GET parameter named 'parent'. Common paths include login pages, redirection handlers, or frame parent references.
    Affected if A script or endpoint exists that processes the 'parent' GET parameter for redirect functionality.
  4. Test redirect behavior with external domain
    Craft a test URL with 'parent' parameter set to an external domain (for example: ?parent=http://example.com) and observe if the application redirects to that external domain without validation or warning.
    Affected if The application redirects to the arbitrary domain specified in the 'parent' parameter without validating it is an internal path.

A user is affected if the system is V-SOL GPON/EPON OLT Platform version 2.03 and contains a script that uses the 'parent' GET parameter in redirects without validating the target is an internal path.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and whitelist-based redirect logic to ensure the 'parent' parameter only allows trusted internal paths, rejecting any attempts to redirect to external domains or unauthorized URLs.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-25282 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-25282 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data