CVE-2025-11713
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 · uneditedInsufficient escaping in the “Copy as cURL” feature could have been used to trick a user into executing unexpected code on Windows. This did not affect the application when running on other operating systems. This vulnerability was fixed in Firefox 144, Firefox ESR 140.4, Thunderbird 144, and Thunderbird 140.4.
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 · moderate confidenceThe 'Copy as cURL' feature in Firefox and Thunderbird insufficiently escaped generated curl commands on Windows, potentially allowing an attacker to inject malicious parameters that could execute unexpected code if the user pasted and ran the generated command. This vulnerability is specific to the Windows platform and was addressed in the patched versions listed.
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< 140.4.0< 144.0< 140.4.0>= 141.0, < 144.0CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
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.
-
Identify installed product and versionOpen Firefox or Thunderbird, go to Help > About to view the exact version numberAffected if Version is < 140.4.0, or >= 141.0 but < 144.0 for either product
-
Confirm operating system is WindowsCheck system properties or run 'systeminfo' command to verify OS is Windows (this vulnerability only affects Windows)Affected if Running Windows and the product version is in the affected range
-
Locate the Copy as cURL featureIn Firefox or Thunderbird on Windows, right-click in a network request within the Developer Tools (Network tab) and look for 'Copy as cURL' optionAffected if The feature exists and is accessible in the installed version
-
Inspect recent clipboard contentCheck Windows clipboard history or manually paste recent clipboard content to look for curl commands with unexpected parameters (such as -o, -J, --resolve, or other curl options not typical for simple request copying)Affected if Clipboard contains curl commands with suspicious or unexpected parameters that were not intentionally added
You are affected if running Windows with Firefox or Thunderbird version in the vulnerable ranges AND you have used the Copy as cURL feature, with potential malicious parameters present in copied commands.
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 · scoped140.4.0144.0
Update affected installations to Firefox 144 (or ESR 140.4) or Thunderbird 144 (or 140.4) or later. Users on Windows should exercise caution with 'Copy as cURL' output until patched.
Firefox 144 (or Firefox ESR 140.4); Thunderbird 144 (or Thunderbird 140.4)
- 1. Determine if Firefox or Thunderbird is installed and note the current version (Help > About Firefox/Thunderbird)
- 2. For Firefox users: Download and install Firefox 144 (or Firefox ESR 140.4 for enterprise environments) from the official Mozilla website
- 3. For Thunderbird users: Download and install Thunderbird 144 (or Thunderbird 140.4) from the official Mozilla website
- 4. After installation, restart the application to complete the update
- 5. Verify the fix by checking the version number (Help > About) matches the target fixed release
- 6. On Windows, test the 'Copy as cURL' feature in Developer Tools to confirm the escaping vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11713 — 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-11713 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