How severe is GHSA-wfxg-v3j4-7qmj?

No CVSS score has been assigned to GHSA-wfxg-v3j4-7qmj yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-wfxg-v3j4-7qmj?

GHSA-wfxg-v3j4-7qmj affects the following packages: github.com/usememos/memos (Go). Ecosystems affected: Go.

How do I fix GHSA-wfxg-v3j4-7qmj?

The records we use list no patched version of github.com/usememos/memos for GHSA-wfxg-v3j4-7qmj. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect GHSA-wfxg-v3j4-7qmj in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/usememos/memos, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-wfxg-v3j4-7qmj if there is no patch (or I can't update yet)?

Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Is GHSA-wfxg-v3j4-7qmj actively exploited in the wild?

No public exploit code has been indexed for GHSA-wfxg-v3j4-7qmj yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-wfxg-v3j4-7qmj?

GHSA-wfxg-v3j4-7qmj has an EPSS (Exploit Prediction Scoring System) score of 2.9%, placing it in the 87th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-wfxg-v3j4-7qmj?

GHSA-wfxg-v3j4-7qmj is classified as Server-Side Request Forgery (SSRF) (CWE-918). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for GHSA-wfxg-v3j4-7qmj?

A Nuclei detection template exists for GHSA-wfxg-v3j4-7qmj, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-wfxg-v3j4-7qmj published, and has it been updated?

GHSA-wfxg-v3j4-7qmj was published on February 27, 2025 and was last updated on March 3, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

Memos Server-Side Request Forgery (SSRF)GHSA-wfxg-v3j4-7qmj

Fix: usememos/memos#4421

GHSA-wfxg-v3j4-7qmj is a Server-Side Request Forgery (SSRF) vulnerability in github.com/usememos/memos. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asCVE-2025-22952GO-2025-3492

Published

Feb 27, 2025

Updated

Mar 3, 2025

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for GHSA-wfxg-v3j4-7qmj.

EPSS Exploitation Probability

via FIRST.org ↗

2.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs87th percentile — riskier than 87% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐹github.com/usememos/memos

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/usememos/memos`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

memosusememos

1 version

0.23.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/usememos/memos, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of github.com/usememos/memos for GHSA-wfxg-v3j4-7qmj. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

How to detect GHSA-wfxg-v3j4-7qmj

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id ghsa-wfxg-v3j4-7qmj -u https://target

Template: Elestio Memos <= v0.24.0 - Server-Side Request Forgery
Severity: critical
Impact: Unauthenticated attackers can exploit SSRF vulnerabilities to access internal services, bypass network security controls, and potentially retrieve sensitive information from internal systems.
Remediation: Upgrade to Memos version 0.24.1 or later that properly validates and restricts URL access.

Template by ProjectDiscovery nuclei-templates (iamnoooob, rootxharsh, pdresearch), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-wfxg-v3j4-7qmj in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works