Cross-account record creation via client-supplied owner IDs
Published Dec 28, 2022 · Updated Apr 10, 2025
Access control failure in Memos 0.9.0 and earlier allows remote authenticated users to create records under another user's identity. API creation handlers decode client-supplied creator or user identifiers into ownership fields instead of deriving those fields solely from the active session. The affected routes require an authenticated session; successful exploitation corrupts record attribution and can alter user-scoped data.
Summary
What happened
Access control failure in Memos 0.9.0 and earlier allows remote authenticated users to create records under another user's identity. API creation handlers decode client-supplied creator or user identifiers into ownership fields instead of deriving those fields solely from the active session. The affected routes require an authenticated session; successful exploitation corrupts record attribution and can alter user-scoped data.
The record
- CVE
- CVE-2022-4800
- Published
- Dec 28, 2022
- Updated
- Apr 10, 2025
- Vendor
- Memos
- Product
- Memos
- Classifications
- CWE-940, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 28, 2022CVE publishedPublication date reported by the CVE source.
- Apr 10, 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=unspecified <0.9.1
What conditions does exploitation require?
What is affected?
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
- huntr.dev bounty proof of conceptproof of concept · unverified
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