CVE-2011-1810 json
The Cascading Style Sheets (CSS) implementation in Google Chrome before 12.0.742.91 does not properly restrict access to the visit history,…
published 2011-06-09 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-1808
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 65%
- public exploits
- 0
- none known
Summary
The Cascading Style Sheets (CSS) implementation in Google Chrome before 12.0.742.91 does not properly restrict access to the visit history, which allows remote attackers to obtain sensitive information via unspecified vectors.
Patch / fix
- google chrome 12.0.742.91
Exploit prediction
1.07% chance of exploitation in the next 30 days, higher than 65% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- Technology feeds
References
-
secunia.com
/advisories/44829
third-party-advisory
- code.google.com /p/chromium/issues/detail?id=75643
-
osvdb.org
/72780
vdb-entry
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14433
vdb-entry, signature
-
exchange.xforce.ibmcloud.com
/vulnerabilities/67893
vdb-entry
- googlechromereleases.blogspot.com /2011/06/chrome-stable-release.html
-
securityfocus.com
/bid/48129
vdb-entry
Sources
- CVE List CVE-2011-1810
- NVD CVE-2011-1810
Fencer Intel 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.