Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2015-0801

Mozilla: Same-origin bypass through anchor navigation (MFSA 2015-40)

Overview

Published
1 Apr 2015
Modified
6 May 2026
High CVE
0 Registry packages
19 OS packages
3 Linux distributions
Yes Fix available

Description

Mozilla Firefox before 37.0, Firefox ESR 31.x before 31.6, and Thunderbird before 31.6 allow remote attackers to bypass the Same Origin Policy and execute arbitrary JavaScript code with chrome privileges via vectors involving anchor navigation, a similar issue to CVE-2015-0818.

Source: OX vulnerability database

Severity

7.5 · HIGH

CVSS 2.0 base score, scored by NVD.

Access vector
Network
Access complexity
Low
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

Weakness: CWE-264

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 7 fixes

Oracle Linux 1 release · 2 packages

fixed 2
thunderbird firefox
Oracle Linux fixes for CVE-2015-0801
ReleasePackageFixed in
7 thunderbird 31.6.0-1.0.1.el7_1
7 firefox +2 31.6.0-2.0.1.el7_1

Red Hat 1 release · 2 packages

fixed 2
thunderbird firefox
Red Hat fixes for CVE-2015-0801
ReleasePackageFixed inAdvisory
7 thunderbird 0:31.6.0-1.el7_1 RHSA-2015:0771
7 firefox +2 0:31.6.0-2.el7_1 RHSA-2015:0766

openSUSE 1 release · 3 packages

fixed 3
firefox-esr mozillathunderbird mozillafirefox
openSUSE fixes for CVE-2015-0801
ReleasePackageFixed inAdvisory
Tumbleweed firefox-esr +3 128.5.1-1.1 openSUSE-SU-2024:14572-1
Tumbleweed mozillathunderbird +4 45.5.1-1.1 openSUSE-SU-2024:10230-1
Tumbleweed mozillafirefox +5 50.1.0-1.1 openSUSE-SU-2024:10071-1

References

Show all 25 references

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.