CVE-2025-62716
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 · uneditedPlane is open-source project management software. Prior to version 1.1.0, an open redirect vulnerability in the ?next_path query parameter allows attackers to supply arbitrary schemes (e.g., javascript:) that are passed directly to router.push. This results in a cross-site scripting (XSS) vulnerability, enabling attackers to execute arbitrary JavaScript in the victim’s browser. The issue can be exploited without authentication and has severe impact, including information disclosure, and privilege escalation and modifications of administrative settings. This issue has been patched in version 1.1.0.
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 · high confidencePlane project management software contains an open redirect vulnerability in the ?next_path query parameter. The parameter value is passed directly to router.push without validation, allowing attackers to supply javascript: URIs that result in arbitrary JavaScript execution in victims' browsers. This can be exploited without authentication.
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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Plane versionLocate the Plane version number in the application UI (typically found in Settings > About, or in the footer of the admin dashboard), or query the API endpoint /api/v1/server-Info or /api/v1/users/me if availableAffected if The installed version is below 1.1.0 (e.g., 1.0.x, 0.x.x)
-
Verify next_path parameter acceptanceSend a request to any Plane page with the query parameter ?next_path=test (such as /auth/login?next_path=test) and observe if the application accepts and reflects this parameter in the response or redirectAffected if The next_path parameter is accepted and processed without error
-
Test for javascript: scheme injectionSubmit a request with ?next_path=javascript:alert(1) to any Plane endpoint (e.g., /auth/login?next_path=javascript:alert(1)) and check if the browser executes the JavaScript code upon navigationAffected if The javascript: URI is not sanitized and executes in the browser context
-
Check authentication requirement for exploitationConfirm the vulnerability can be triggered without authenticating to Plane by accessing the vulnerable endpoint as an unauthenticated userAffected if The exploit works without requiring valid credentials
-
Review server response headersInspect HTTP responses from the Plane server for version-revealing headers or examine the HTML source for version strings embedded in scripts or meta tagsAffected if Server exposes version information confirming a version below 1.1.0
An environment is affected if the installed Plane version is below 1.1.0 and the application accepts and processes the next_path query parameter without sanitizing javascript: or other arbitrary URI schemes.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scopedUpgrade Plane to version 1.1.0 or later, which includes proper validation of the next_path parameter to prevent arbitrary scheme injection.
1.1.0
- Verify current Plane installation version to confirm it is prior to 1.1.0
- Review the official Plane release notes and migration guide for version 1.1.0
- Create a full backup of the Plane database and configuration files
- Stop the Plane service
- Upgrade Plane to version 1.1.0 following the official upgrade instructions (typically by pulling the latest Docker image or updating the installation method used)
- Start the Plane service and verify it is running
- Test that the ?next_path parameter is now properly sanitized and does not accept javascript: or other arbitrary schemes
- Verify that authentication, authorization, and core project management functions work correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62716 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-62716 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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