dbcve.org
MemosApplication · Usememos

CVE-2025-50738

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-29
Fix available
A fix is available. Upgrade to after 0.24.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Memos application, up to version v0.24.3, allows for the embedding of markdown images with arbitrary URLs. When a user views a memo containing such an image, their browser automatically fetches the image URL without explicit user consent or interaction beyond viewing the memo. This can be exploited by an attacker to disclose the viewing user's IP address, browser User-Agent string, and potentially other request-specific information to the attacker-controlled server, leading to information disclosure and user tracking.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Memos application v0.24.3 and prior allows arbitrary URL embedding in markdown images. When users view memos containing attacker-controlled image URLs, their browsers automatically issue GET requests to those URLs, exposing the users' IP addresses, User-Agent strings, and request metadata to the attacker's server without any user interaction beyond viewing the memo.

MitigationImplement URL validation to restrict external image domains, or deploy a reverse proxy/URL sanitizer that serves external images through the application's own server to prevent direct browser requests to arbitrary URLs.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MemosApplication
Affected:<= 0.24.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Memos application version
    Access the Memos installation's system settings or check the version file/API endpoint (typically /api/v1/system). Compare the reported version number to the affected range: <= 0.24.3.
    Affected if The installed version is 0.24.3 or any earlier version.
  2. Inspect memos for external image URLs
    Query the database or exported memo content for markdown image syntax using external domains (e.g., search for patterns like ![alt](http:// or ![alt](https:// in memo content). Identify any image links pointing to domains other than the application's own domain.
    Affected if Any memos contain markdown images referencing external/untrusted domains.
  3. Verify URL validation configuration
    Examine the Memos configuration files (memo.yaml, .env, or similar) or admin settings for any URL validation, domain allowlist/blocklist, or external image proxy settings. Check if restrictions on external image domains are defined.
    Affected if No URL validation or domain restrictions are configured, or the configuration permits arbitrary external URLs.
  4. Test browser request behavior
    Create a test memo with an image tag pointing to a controlled external test URL (e.g., a logging endpoint). View the memo and inspect whether the browser automatically issues a GET request to the external URL without user interaction.
    Affected if The browser automatically fetches the external image URL when viewing the memo, without clicking or interacting with the image.

A user is affected if they run Memos version 0.24.3 or earlier and their instance displays memos containing unrestricted external image URLs without proper URL validation configured.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 0.24.3
Interim mitigation

Implement URL validation to restrict external image domains, or deploy a reverse proxy/URL sanitizer that serves external images through the application's own server to prevent direct browser requests to arbitrary URLs.

Fix this in Memos Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-50738 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-50738 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data