CVE-2011-1774 in the critical feed json
WebKit in Apple Safari before 5.0.6 has improper libxslt security settings, which allows remote attackers to create arbitrary files, and co…
published 2011-07-21 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-1772
- cvss
- 8.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 43.2%
- EPSS 43.2% chance of exploitation in 30 days, percentile 98%
- public exploits
- 3
- Metasploit, Exploit-DB
Summary
WebKit in Apple Safari before 5.0.6 has improper libxslt security settings, which allows remote attackers to create arbitrary files, and consequently execute arbitrary code, via a crafted web site. NOTE: this may overlap CVE-2011-1425.
Patch / fix
Timeline
- First public exploit (Metasploit exploit/windows/browser/safari_xslt_output)
- Published
Exploit prediction
43.20% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit exploit/windows/browser/safari_xslt_output Apple Safari Webkit libxslt Arbitrary File Creation metasploit exploit, excellent rank, 2011-07-20
- Metasploit auxiliary/server/webkit_xslt_dropper Cross Platform Webkit File Dropper metasploit auxiliary, normal rank
- EDB-17993 Apple Safari Webkit - libxslt Arbitrary File Creation (Metasploit) remote, 2011-10-18
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 8.8 | AV:N/AC:M/Au:N/C:N/I:C/A:C |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
lists.apple.com
/archives/security-announce/2011//Jul/msg00002.html
vendor-advisory, patch
-
lists.apple.com
/archives/Security-announce/2011//Oct/msg00001.html
vendor-advisory
-
lists.apple.com
/archives/Security-announce/2011//Oct/msg00000.html
vendor-advisory
-
support.apple.com
/kb/HT4808
vendor-advisory
-
securityreason.com
/securityalert/8481
third-party-advisory
- support.apple.com /kb/HT4981
- support.apple.com /kb/HT4999
Sources
- CVE List CVE-2011-1774
- NVD CVE-2011-1774
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.