CVE-2025-22952

CVE-2025-22952 is a critical-severity vulnerability in Usememos Memos with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-918.

Key facts

Description

elestio memos v0.23.0 is vulnerable to Server-Side Request Forgery (SSRF) due to insufficient validation of user-supplied URLs, which can be exploited to perform SSRF attacks.

Frequently asked questions

What is CVE-2025-22952?
elestio memos v0.23.0 is vulnerable to Server-Side Request Forgery (SSRF) due to insufficient validation of user-supplied URLs, which can be exploited to perform SSRF attacks.
How severe is CVE-2025-22952?
CVE-2025-22952 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2025-22952 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (85th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-22952?
CVE-2025-22952 affects Usememos Memos. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-22952?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
Does CVE-2025-22952 have an EU (EUVD) identifier?
Yes. CVE-2025-22952 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-5566.
When was CVE-2025-22952 published?
CVE-2025-22952 was published on 2025-02-27 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Usememos Memos

All CVEs affecting Usememos Memos →

Other CWE-918 (Server-Side Request Forgery (SSRF)) vulnerabilities

Browse all CWE-918 (Server-Side Request Forgery (SSRF)) vulnerabilities →