CVE-2025-3523
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 · uneditedWhen an email contains multiple attachments with external links via the X-Mozilla-External-Attachment-URL header, only the last link is shown when hovering over any attachment. Although the correct link is used on click, the misleading hover text could trick users into downloading content from untrusted sources. This vulnerability was fixed in Thunderbird 137.0.2 and Thunderbird 128.9.2.
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 confidenceIn Thunderbird, when emails contain multiple attachments with external links specified via the X-Mozilla-External-Attachment-URL header, the hover tooltip incorrectly displays only the last defined URL regardless of which attachment the user hovers over. While the actual click action uses the correct per-attachment URL, the misleading hover text could cause users to trust and download malicious content from untrusted sources.
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< 128.9.2>= 129.0, < 137.0.2CVSS 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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:H/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Check if Thunderbird is installed and get its versionIn Thunderbird, go to Help > About Thunderbird. The version number will be displayed in the dialog that opens. On Linux, you can also run 'thunderbird --version' in terminal. On Windows, check Add/Remove Programs or the application properties.Affected if Version is less than 128.9.2, or greater than or equal to 129.0 but less than 137.0.2
-
Identify emails with external attachment URLsUse Thunderbird's search or message filters to find emails containing the header 'X-Mozilla-External-Attachment-URL'. You can also view message source (View > Message Source) for specific emails to inspect headers.Affected if Emails exist that contain multiple attachments with X-Mozilla-External-Attachment-URL headers defined
-
Verify the tooltip behavior with multiple external attachmentsReceive or open an email with multiple attachments where each has an X-Mozilla-External-Attachment-URL header defined. Hover the mouse cursor over each attachment individually and observe the URL shown in the tooltip.Affected if The tooltip shows the same URL for all attachments instead of the correct per-attachment URL
You are affected if your Thunderbird version is within the vulnerable range AND you handle emails containing multiple attachments with X-Mozilla-External-Attachment-URL headers, where hovering shows the same URL for every attachment.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scoped128.9.2137.0.2
Upgrade Thunderbird to version 137.0.2 or 128.9.2 or later. Users should verify attachment sources through alternative means rather than relying on hover text until patched.
Thunderbird 128.9.2 (ESR) or Thunderbird 137.0.2 (standard release)
- Check current Thunderbird version by navigating to Help > About Thunderbird
- Download Thunderbird 128.9.2 (for users on the Extended Support Release channel) or Thunderbird 137.0.2 (for users on the standard release channel) from the official Mozilla Thunderbird website
- Close Thunderbird completely before installing the update
- Install the downloaded Thunderbird update by running the installer and following the prompts
- After installation, verify the version by checking Help > About Thunderbird to confirm the version number matches the expected fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3523 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-3523 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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