Skip to content

Insecure permissions in UserSerializer

Low
twtaylor published GHSA-cjh4-q763-cc48 May 21, 2025

Package

No package listed

Affected versions

< 0.23

Patched versions

=> 0.23

Description

Summary

Plane < 0.23 has insecure permissions in UserSerializer that allows users to change (meant to be) read-only fields.

PoC

Users can change their email by sending a PATCH request directly to the /api/users/me endpoint with the following body:

{"email":"[email protected]"}

Impact

User can modify some fields such as email where it should not be possible by design, this can lead to account takeover when chained with another vulnerability such as cross-site scripting (XSS).

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
Low
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
Low
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:L/PR:L/UI:R/S:U/C:N/I:L/A:N

CVE ID

CVE-2025-48070

Weaknesses

No CWEs

Credits