Cross-site request forgery via missing request validation
Published Dec 29, 2022 · Updated Apr 10, 2025
Cross-site request forgery in Memos before 0.9.1 allows remote attackers to perform state-changing actions through a victim's session. The server registers API routes without CSRF middleware and issues session cookies without SameSite=Strict, so cross-site requests are accepted with the victim's cookie. Exploitation requires a signed-in victim to visit attacker-controlled content and is bounded to actions permitted by that victim's account.
Summary
What happened
Cross-site request forgery in Memos before 0.9.1 allows remote attackers to perform state-changing actions through a victim's session. The server registers API routes without CSRF middleware and issues session cookies without SameSite=Strict, so cross-site requests are accepted with the victim's cookie. Exploitation requires a signed-in victim to visit attacker-controlled content and is bounded to actions permitted by that victim's account.
The record
- CVE
- CVE-2022-4846
- Published
- Dec 29, 2022
- Updated
- Apr 10, 2025
- Vendor
- Memos
- Product
- Memos
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 29, 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 CSRF 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