FirefoxWeb browser · Mozilla
CVE-2022-22754
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 · uneditedIf a user installed an extension of a particular type, the extension could have auto-updated itself and while doing so, bypass the prompt which grants the new version the new requested permissions. This vulnerability affects Firefox < 97, Thunderbird < 91.6, and Firefox ESR < 91.6.
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 confidenceA vulnerability in Firefox, Thunderbird, and Firefox ESR allows extensions of a particular type to auto-update and bypass the permission prompt that normally notifies users when new permissions are requested. This could allow malicious extensions to silently escalate their privileges.
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
FirefoxWeb browser
< 97.0
Firefox EsrWeb browser
< 91.6< 91.6CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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.
-
Check installed Firefox versionNavigate to Help > About Firefox or enter 'about:support' in the address bar to view the version number under Application BasicsAffected if Version is below 97.0 (e.g., 96.x or earlier)
-
Check installed Firefox ESR versionNavigate to Help > About Firefox ESR to view the version numberAffected if Version is below 91.6 (e.g., 91.5.x or earlier)
-
Check installed Thunderbird versionNavigate to Help > About Thunderbird to view the version numberAffected if Version is below 91.6 (e.g., 91.5.x or earlier)
-
Verify extension auto-update is enabledGo to Add-ons and Themes (about:addons), click the gear icon, and check that 'Update Add-ons Automatically' is checked under the Updates sectionAffected if Auto-update for extensions is enabled and browser version is in the affected range
A user is affected if their browser (Firefox, Firefox ESR, or Thunderbird) is below the fixed version AND they have extensions installed with auto-update capability enabled.
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 · scoped91.697.0
Update affected browsers to Firefox 97, Thunderbird 91.6, or Firefox ESR 91.6 or later to patch the vulnerability.
Firefox 97.0, Firefox ESR 91.6, or Thunderbird 91.6
- Upgrade Firefox to version 97.0 or later
- Upgrade Firefox ESR to version 91.6 or later
- Upgrade Thunderbird to version 91.6 or later
- After upgrading, verify the installed browser/Thunderbird version matches the fixed release via Help > About
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Firefox
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22754 — 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-2022-22754 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