Authenticated username changes via unfiltered update parameter
Published Dec 1, 2025 · Updated Dec 1, 2025
Authorization bypass in FeehiCMS 2.1.1 allows remote authenticated users to change account usernames through user-update requests. The user-update backend accepts a client-supplied username field even though the interface marks it read-only, without omitting the field or enforcing an allowed-field list. Access to the backend user module is required, and successful exploitation changes the stored username associated with a user record.
Summary
What happened
Authorization bypass in FeehiCMS 2.1.1 allows remote authenticated users to change account usernames through user-update requests. The user-update backend accepts a client-supplied username field even though the interface marks it read-only, without omitting the field or enforcing an allowed-field list. Access to the backend user module is required, and successful exploitation changes the stored username associated with a user record.
The record
- CVE
- CVE-2025-63523
- Published
- Dec 1, 2025
- Updated
- Dec 1, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-125, T1098
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 1, 2025CVE publishedPublication date reported by the CVE source.
- Dec 1, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- FeehiCMS read-only username parameter 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