Skip to content
Fencer Vulns
medium 6.5

CVE-2023-5487 json

Inappropriate implementation in Fullscreen in Google Chrome prior to 118.0.5993.70 allowed an attacker who convinced a user to install a ma…

published 2023-10-11 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-57801

cvss
6.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 50%
public exploits
0
none known

Summary

Inappropriate implementation in Fullscreen in Google Chrome prior to 118.0.5993.70 allowed an attacker who convinced a user to install a malicious extension to bypass navigation restrictions via a crafted Chrome Extension. (Chromium security severity: Medium)

Patch / fix

  • google chrome 118.0.5993.70
  • chromium Debian 12 118.0.5993.70-1~deb12u1
  • chromium Debian 14, Debian 13 118.0.5993.70-1

debian advisories DEBIAN-CVE-2023-5487

  • chromium openSUSE Tumbleweed 118.0.5993.70-1.1
  • opera openSUSE Leap 15.5 NonFree 104.0.4944.23-lp155.3.15.1
  • opera openSUSE Leap 15.4 NonFree 104.0.4944.23-lp154.2.56.1
  • chromium Package Hub 15 SP5, Package Hub 15 SP4, openSUSE Leap 15.5 +1 more 118.0.5993.70-bp155.2.46.1

opensuse advisories openSUSE-SU-2024:13317-1openSUSE-SU-2024:13335-1openSUSE-SU-2023:0338-1openSUSE-SU-2023:0337-1openSUSE-SU-2023:0300-1

  • qt6-qtwebengine Alpine 3.24, Alpine 3.23, Alpine 3.22 +3 more 6.6.0-r1

alpine advisories ALPINE-CVE-2023-5487

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Exploit prediction

0.62% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

Affected products

  • Google Chrome

Classification

Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.