Skip to content
Fencer Intel
critical 9.8

CVE-2023-4696 json

Improper Access Control in usememos/memos

published 3y ago modified 4mo ago also GHSA-j2gj-g3p9-7mrr , GO-2023-2038 , EUVD-2023-2530

cvss
9.8
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.1%
EPSS 1.1% chance of exploitation in 30 days, percentile 66%
public exploits
0
none known

Summary

Improper Access Control 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

Is CVE-2023-4696 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
yes
Technical impact
total
Assessed
2y ago

Exploit prediction

1.12% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-15).

CVSS scores

assigned by version score vector
CNA 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/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

References

Sources

Fencer Intel 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.