FirefoxWeb browser · Mozilla
CVE-2022-22761
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 · uneditedWeb-accessible extension pages (pages with a moz-extension:// scheme) were not correctly enforcing the frame-ancestors directive when it was used in the Web Extension's Content Security Policy. 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 confidenceWeb extension pages using the moz-extension:// scheme were not correctly enforcing the frame-ancestors directive in the Content Security Policy, potentially allowing clickjacking or unauthorized framing of extension pages.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Check Firefox browser versionOpen Firefox and navigate to about:support, or run `firefox --version` in terminal. Locate the 'Version' field.Affected if Version is below 97.0 (e.g., 96.x or earlier)
-
Check Firefox ESR versionOpen Firefox ESR and navigate to about:support, or run `firefox --version` in terminal. Locate the 'Version' field.Affected if Version is below 91.6 (e.g., 91.5.x or earlier)
-
Check Thunderbird versionOpen Thunderbird and navigate to Help > About, or run `thunderbird --version` in terminal.Affected if Version is below 91.6 (e.g., 91.5.x or earlier)
-
Identify installed extensionsIn Firefox/Thunderbird, navigate to about:addons and review the list of installed extensions and themes.Affected if Any browser extensions or add-ons are installed, as these use the moz-extension:// scheme and could be subject to framing
You are affected if your Firefox version is below 97.0, Firefox ESR is below 91.6, or Thunderbird is below 91.6, and you have any extensions or add-ons installed that utilize the moz-extension:// scheme.
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
Upgrade to Firefox 97+, Thunderbird 91.6+, or Firefox ESR 91.6+ to apply the patched Content Security Policy enforcement for extension pages.
Firefox 97.0, Firefox ESR 91.6, or Thunderbird 91.6
- For Firefox users: Update to version 97.0 or later via Help > About Firefox > Update
- For Firefox ESR users: Update to version 91.6 or later via Help > About Firefox > Update
- For Thunderbird users: Update to version 91.6 or later via Help > About Thunderbird > Check for Updates
- Alternatively, download the latest versions from the official Mozilla website: www.mozilla.org
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Firefox
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22761 — 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-22761 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