CVE-2025-10530
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 · uneditedSpoofing issue in the WebAuthn component in Firefox for Android. This vulnerability was fixed in Firefox 143 and Thunderbird 143.
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 confidenceA spoofing vulnerability in the WebAuthn component of Firefox for Android allows attackers to potentially impersonate legitimate authentication sites, tricking users into authenticating to malicious sites. This could enable credential theft or unauthorized access to user accounts.
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< 143.0< 143.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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 Firefox for Android installationCheck if Mozilla Firefox for Android is installed on the device by examining installed applications or running 'adb shell pm list packages | grep firefox'Affected if The package 'org.mozilla.firefox' is present on the device
-
Check Firefox for Android versionOpen Firefox for Android, navigate to Settings > About Firefox, or use 'adb shell dumpsys package org.mozilla.firefox' to view version informationAffected if The displayed version number is less than 143.0 (for example, 142.x, 141.x, etc.)
-
Identify Thunderbird installationCheck if Thunderbird is installed by examining installed applications on the deviceAffected if Thunderbird is present on the device
-
Check Thunderbird versionOpen Thunderbird, navigate to Settings > About Thunderbird, or use ADB to query the package version similar to FirefoxAffected if The displayed version number is less than 143.0
The environment is affected if Mozilla Firefox for Android or Thunderbird is installed with a version number below 143.0, since the WebAuthn spoofing vulnerability exists in those versions.
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 · scoped143.0
Update Firefox for Android to version 143 or later, and Thunderbird to version 143 or later. Users should also be cautious of authentication requests from untrusted sources.
Firefox 143.0 and Thunderbird 143.0
- Check the current version of Firefox or Thunderbird by navigating to Menu > Help > About Firefox/Thunderbird
- For Firefox: Open the application and go to Menu > Help > About Firefox > Check for Updates
- For Thunderbird: Open the application and go to Menu > Help > About Thunderbird > Check for Updates
- Allow the update to download and install version 143.0
- Restart the application when prompted to complete the installation
- Verify the installed version is 143.0 or higher by returning to Menu > Help > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10530 — 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-10530 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