Skip to content
Fencer Vulns
high 7.1

CVE-2023-2460 json

Insufficient validation of untrusted input in Extensions in Google Chrome prior to 113.0.5672.63 allowed an attacker who convinced a user t…

published 2023-05-02 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-33945

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

Summary

Insufficient validation of untrusted input in Extensions in Google Chrome prior to 113.0.5672.63 allowed an attacker who convinced a user to install a malicious extension to bypass file access checks via a crafted HTML page. (Chromium security severity: Medium)

Patch / fix

  • google chrome 113.0.5672.63
  • chromium Debian 14, Debian 13, Debian 12 113.0.5672.63-1

debian advisories DEBIAN-CVE-2023-2460

  • chromium openSUSE Tumbleweed 113.0.5672.92-1.1
  • chromium Package Hub 15 SP4, openSUSE Leap 15.4 113.0.5672.126-bp154.2.87.1

opensuse advisories openSUSE-SU-2024:12922-1openSUSE-SU-2024:12948-1openSUSE-SU-2023:0117-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-2460 updated cvss 6.5

chromium-browser: Insufficient validation of untrusted input in Extensions

  • 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

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

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

CVSS scores

assigned by version score vector
NVD 3.1 7.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/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.