Authenticated privilege escalation via client-controlled user identifier
Published Jun 2, 2023 · Updated Jan 8, 2025
Incorrect authorization in Mobatime Web Application 06.7.22 and earlier allows remote authenticated users to impersonate other users. The AJAX API accepts an unsigned, client-controlled user identifier and uses it for authorization instead of binding requests to the authenticated session. Any authenticated account can substitute another identifier, exposing that user's content and granting the associated application privileges.
Summary
What happened
Incorrect authorization in Mobatime Web Application 06.7.22 and earlier allows remote authenticated users to impersonate other users. The AJAX API accepts an unsigned, client-controlled user identifier and uses it for authorization instead of binding requests to the authenticated session. Any authenticated account can substitute another identifier, exposing that user's content and granting the associated application privileges.
The record
- CVE
- CVE-2023-3033
- Published
- Jun 2, 2023
- Updated
- Jan 8, 2025
- Vendor
- Mobatime
- Product
- Mobatime Web Application
- Classifications
- CWE-863, CAPEC-180, CAPEC-233, T1068
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 2, 2023CVE publishedPublication date reported by the CVE source.
- Jan 8, 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 <=06.7.22
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.
Weakness, pattern, technique
Public exploit references
- Client-controlled user identifier impersonation walkthroughfunctional · 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