Account email overwrite via writable serializer field
Published May 21, 2025 · Updated May 22, 2025
Authorization weakness in Plane before 0.23 allows remote authenticated users to overwrite the associated account email through a direct API request. UserSerializer accepts the email field in a PATCH to the current-user API endpoint instead of enforcing the field as read-only, so the supplied address is persisted. A valid account is required; the write changes account identity data and enables account takeover only when chained with another flaw such as XSS.
Summary
What happened
Authorization weakness in Plane before 0.23 allows remote authenticated users to overwrite the associated account email through a direct API request. UserSerializer accepts the email field in a PATCH to the current-user API endpoint instead of enforcing the field as read-only, so the supplied address is persisted. A valid account is required; the write changes account identity data and enables account takeover only when chained with another flaw such as XSS.
The record
- CVE
- CVE-2025-48070
- Published
- May 21, 2025
- Updated
- May 22, 2025
- Vendor
- Plane
- Product
- Plane
- Classifications
- CWE-276, T1098
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 21, 2025CVE publishedPublication date reported by the CVE source.
- May 22, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.23
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Authenticated email-change PATCH proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo