The "Forget about this site" feature in the History pane is intended to remove all saved user data that indicates a user has visited a site.
Noroxi assessment
Priority: Monitor (action score 26/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.1% (FIRST EPSS); higher than 67.7% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: firefox-esr (Debian:12) 68.1.0esr-1; firefox (Red Hat:enterprise_linux:8::appstream) 0:68.1.0-1.el8_0; firefox-debuginfo (Red Hat:enterprise_linux:8::appstream) 0:68.1.0-1.el8_0.
Low priority for now. Upgrade to firefox-esr (Debian:12) 68.1.0esr-1; firefox (Red Hat:enterprise_linux:8::appstream) 0:68.1.0-1.el8_0; firefox-debuginfo (Red Hat:enterprise_linux:8::appstream) 0:68.1.0-1.el8_0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
The "Forget about this site" feature in the History pane is intended to remove all saved user data that indicates a user has visited a site. This includes removing any HTTP Strict Transport Security (HSTS) settings received from sites that use it. Due to a bug, sites on the pre-load list also have their HSTS setting removed. On the next visit to that site if the user specifies an http: URL rather than secure https: they will not be protected by the pre-loaded HSTS setting. After that visit the site's HSTS setting will be restored. This vulnerability affects Firefox < 69 and Firefox ESR < 68.1.
- Published
- Sep 27, 2019
- Updated
- Jun 16, 2026
- EPSS
- 1.1% · 67th percentile
- CWE
- CWE-665
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| mozilla | firefox | cpe:2.3:a:mozilla:firefox |
| mozilla | firefox esr | cpe:2.3:a:mozilla:firefox_esr |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- mozilla firefoxbefore 69.0
- mozilla firefox esrbefore 68.1.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (mozilla). Independent of NVD's CPE analysis and usually ahead of it.
Mozilla Firefox
- unspecified and later · before 69affected
Mozilla Firefox ESR
- unspecified and later · before 68.1affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | firefox-esr | before 68.1.0esr-1 | 68.1.0esr-1 |
| Red Hat:enterprise_linux:8::appstream | firefox | before 0:68.1.0-1.el8_0 | 0:68.1.0-1.el8_0 |
| Red Hat:enterprise_linux:8::appstream | firefox-debuginfo | before 0:68.1.0-1.el8_0 | 0:68.1.0-1.el8_0 |
| Red Hat:enterprise_linux:8::appstream | firefox-debugsource | before 0:68.1.0-1.el8_0 | 0:68.1.0-1.el8_0 |
Same product
mozilla: all recordsOther highest-scoring records for the same primary product.
- CVE-2010-3765Mozilla Firefox 3.5.x through 3.5.14 and 3.6.x through 3.6.11, Thunderbird 3.1.6 before 3.1.6 and 3.0.x before 3.0.10, and SeaMonkey 2.x befKEV94Now
- CVE-2019-11708Insufficient vetting of parameters passed with the Prompt:Open IPC message between child and parent processes can result in the non-sandboxeKEV87Now
- CVE-2015-4495The PDF reader in Mozilla Firefox before 39.0.3, Firefox ESR 38.x before 38.1.1, and Firefox OS before 2.2 allows remote attackers to bypassKEV86Now
Published before and after this one in the same product
- ← EarlierCVE-2019-11744Sep 27, 2019 · Some HTML elements, such as <title> and <textarea>, can contain literal angle brackets without treating them as markup.24Monitor
- ← EarlierCVE-2019-11746Sep 27, 2019 · A use-after-free vulnerability can occur while manipulating video elements if the body is freed while still in use.36Monitor
- Later →CVE-2019-11748Sep 27, 2019 · WebRTC in Firefox will honor persisted permissions given to sites for access to microphone and camera resources even when in a third-party c26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:firefox-esr | 68.1.0esr-1 · Debian:12 | Package registry (OSV) |
| red hat:firefox | 0:68.1.0-1.el8_0 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:firefox-debuginfo | 0:68.1.0-1.el8_0 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:firefox-debugsource | 0:68.1.0-1.el8_0 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-665 · Improper InitializationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.