CVE-2022-4799 json
Authorization Bypass Through User-Controlled Key in usememos/memos
published 2022-12-28 3 y ago modified 2026-06-17 4 mo ago also GHSA-jvq8-w7qv-hqp6 , GO-2022-1239 , EUVD-2022-7671
- cvss
- 8.6
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 57%
- public exploits
- 0
- none known
Summary
Authorization Bypass Through User-Controlled Key in GitHub repository usememos/memos prior to 0.9.1.
Patch / fix
- go github.com/usememos/memos 0.9.1
- usememos usememos/memos 0.9.1
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 19 mo ago
Exploit prediction
0.81% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- huntr.dev https://huntr.dev/bounties/c5d70f9d-b7a7-4418-9368-4566a8143e79 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 8.6 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L |
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/usememos/memos | <0.9.1 |
0.9.1 |
Affected products
- usememos usememos/memos
Classification
References
-
github.com
/usememos/memos/commit/3556ae4e651d9443dc3bb8a170dd3cc726517a53
web, patch, third-party-advisory
-
huntr.dev
/bounties/c5d70f9d-b7a7-4418-9368-4566a8143e79
web, exploit, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-4799
advisory
-
github.com
/usememos/memos
package
-
github.com
/advisories/GHSA-jvq8-w7qv-hqp6
advisory
Sources
- CVE List CVE-2022-4799
- GitHub Advisory GHSA-jvq8-w7qv-hqp6
- NVD CVE-2022-4799
- OSV GO-2022-1239
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.