Skip to content

Exposure of User Email (PII and part of credential) in GET Parameter - Incorrect Code

Low
sriramveeraghanta published GHSA-8rvg-7w43-p2w2 Apr 7, 2026

Package

No package listed

Affected versions

<= v1.0.0 Latest

Patched versions

1.3.0

Description

Summary

A vulnerability was identified in Plane's authentication flow where a user's email address is included as a query parameter in the URL during error handling (e.g., when an invalid magic code is submitted). Transmitting personally identifiable information (PII) via GET request query strings is classified as an insecure design practice under CWE-598 and CWE-200.
The affected code path is located in the authentication utility module (packages/utils/src/auth.ts).

Impact

Embedding user email addresses in URLs creates multiple avenues for unintended disclosure. Query strings are persisted in browser history, and may be captured in server, proxy, CDN, or load-balancer access logs. When users navigate away from the error page, the full URL — including the email — can be transmitted to external sites via the HTTP Referer header. Third-party analytics, click-tracking services, and mail client link prefetchers may also receive or cache the exposed address.

Because the email also serves as the user's login identifier, its exposure elevates account-takeover risk when combined with credential reuse or compromised recovery channels. Additionally, uncontrolled persistence of PII across logs and third-party systems may present compliance concerns under privacy regulations such as GDPR.References
CWE-598: Information Exposure Through Query Strings in GET Request
CAPEC-37: Retrieve Embedded Sensitive Data
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor https://cwe.mitre.org/data/definitions/200.html

Credits

This vulnerability was responsibly disclosed by an independent security researcher @mbiesiad . We thank them for their contribution to the security of the Plane platform.

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
High
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:N

CVE ID

CVE-2026-27949

Weaknesses

Exposure of Sensitive Information to an Unauthorized Actor

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Learn more on MITRE.

Use of GET Request Method With Sensitive Query Strings

The web application uses the HTTP GET method to process a request and includes sensitive information in the query string of that request. Learn more on MITRE.

Credits