Authenticated memo deletion via brute-forced post IDs
Published Dec 28, 2022 · Updated Apr 10, 2025
Improper access control in Memos 0.9.0 and earlier allows remote authenticated users to delete other users' memos by guessing numeric IDs. The memo deletion path treats a brute-forced post identifier as sufficient authority to remove another user's record. A valid low-privilege session and a target memo ID are required; successful exploitation deletes content without broader reported impact.
Summary
What happened
Improper access control in Memos 0.9.0 and earlier allows remote authenticated users to delete other users' memos by guessing numeric IDs. The memo deletion path treats a brute-forced post identifier as sufficient authority to remove another user's record. A valid low-privilege session and a target memo ID are required; successful exploitation deletes content without broader reported impact.
The record
- CVE
- CVE-2022-4797
- Published
- Dec 28, 2022
- Updated
- Apr 10, 2025
- Vendor
- Memos
- Product
- Memos
- Classifications
- CWE-307, T1485
- 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 brute-force post deletion 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