XSLT document loading did not correctly propagate the source document which bypassed its CSP. This vulnerability was fixed in Firefox 141, Firefox ESR 128.13, Firefox ESR 140.1, Thunderbird 141, Thunderbird 128.13, and Thunderbird 140.1.
Security readout for executives and security teams
Plain-English summary
A flaw in Firefox and Thunderbird allowed XSLT content to bypass a document’s Content Security Policy. With user interaction, malicious content could potentially expose sensitive information or alter content that the policy should protect. Mozilla has released fixed versions.
Executive priority
Treat this as a high-priority endpoint update because successful exploitation could undermine browser-enforced security controls and affect sensitive data. Fixed releases are available, so organizations should accelerate deployment and track exceptions. No source supplied here establishes active exploitation.
Technical view
XSLT document loading failed to propagate the source document correctly, allowing transformed content to evade its CSP. The CVSS 3.1 score is 8.1: network-accessible, low complexity, no privileges required, user interaction required, with high confidentiality and integrity impact but no rated availability impact.
Likely exposure
Assess Firefox and Thunderbird installations against the applicable fixed releases: 141, ESR 128.13, and ESR 140.1. The supplied sources do not establish complete vulnerable version ranges, so exposure for older or unsupported branches requires vendor confirmation.
Exploitation context
The CVSS vector indicates remote reachability without authentication but requires user interaction. The source bundle reports that this CVE is not in CISA KEV, and it provides no evidence of active exploitation. Absence from KEV does not prove exploitation has never occurred.
Researcher notes
This is categorized as CWE-693, Protection Mechanism Failure. The bundle lists fixed release numbers within its affected section, while Mozilla’s description identifies them as fixed versions. Complete vulnerable-version boundaries, exploitation indicators, and attack-specific prerequisites are not supplied; researchers should avoid inferring them.
Mitigation direction
Update Firefox to 141, ESR 128.13, ESR 140.1, or a later applicable supported release.
Update Thunderbird to 141, 128.13, 140.1, or a later applicable supported release.
Check Mozilla guidance for branch-specific deployment details and subsequent superseding releases.
Prioritize updates on endpoints that process untrusted web or message content.
Validation and detection
Inventory Firefox and Thunderbird versions across endpoints, including ESR channels.
Confirm every installation meets or exceeds its applicable fixed version.
Review software-management reports for failed, deferred, or unmanaged updates.
Re-scan endpoints after deployment and document remaining exceptions.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-693: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
2ADP providers
9Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-693 · source CWE mapping
Protection Mechanism Failure
Protection Mechanism Failure represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.