Skip to content
Fencer Vulns
medium 6.1

CVE-2023-5480 json

Inappropriate implementation in Payments in Google Chrome prior to 119.0.6045.105 allowed a remote attacker to bypass XSS preventions via a…

published 2023-11-01 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-57794

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

Summary

Inappropriate implementation in Payments in Google Chrome prior to 119.0.6045.105 allowed a remote attacker to bypass XSS preventions via a malicious file. (Chromium security severity: High)

Patch / fix

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

debian advisories DEBIAN-CVE-2023-5480

  • chromium openSUSE Tumbleweed 119.0.6045.123-1.1
  • chromium Package Hub 15 SP5, Package Hub 15 SP4, openSUSE Leap 15.5 +1 more 119.0.6045.123-bp155.2.55.1
  • gn Package Hub 15 SP5, Package Hub 15 SP4, openSUSE Leap 15.5 +1 more 0.20231023-bp155.5.3.1

opensuse advisories openSUSE-SU-2024:13419-1openSUSE-SU-2024:13423-1openSUSE-SU-2023:0368-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2023-5480 updated cvss 8.8

chromium-browser: Inappropriate implementation in Payments

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

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

CVSS scores

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

Affected products

  • Google Chrome

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation
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.