CVE-2023-4697 json
Improper Privilege Management in usememos/memos
published 2023-09-01 3 y ago modified 2026-06-17 4 mo ago also GHSA-5j6p-59cj-j6cp , GO-2023-2036 , EUVD-2023-2434
- cvss
- 8.8
- 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 58%
- public exploits
- 0
- none known
Summary
Improper Privilege Management in GitHub repository usememos/memos prior to 0.13.2.
Patch / fix
- go github.com/usememos/memos 0.13.2
- usememos usememos/memos 0.13.2
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- 2 y ago
Exploit prediction
0.85% chance of exploitation in the next 30 days, higher than 58% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- huntr.dev https://huntr.dev/bounties/3ff3325a-1dcb-4da7-894d-81a9cf726d81 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/usememos/memos | <0.13.2 |
0.13.2 |
Affected products
- usememos usememos/memos
Classification
- Weakness
-
- CWE-269 Improper Privilege Management
References
-
github.com
/usememos/memos/commit/c9aa2eeb9852047e4f41915eb30726bd25f07ecd
web, patch
-
huntr.dev
/bounties/3ff3325a-1dcb-4da7-894d-81a9cf726d81
web, exploit, patch, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2023-4697
advisory
-
github.com
/usememos/memos
package
-
github.com
/advisories/GHSA-5j6p-59cj-j6cp
advisory
Sources
- CVE List CVE-2023-4697
- GitHub Advisory GHSA-5j6p-59cj-j6cp
- NVD CVE-2023-4697
- OSV GO-2023-2036
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.