Skip to content

Vendor

w3 vulnerabilities

11 published CVES affecting w3, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
11
Critical
0
High
7
Medium
3
Low
1
Unscored
0
CISA KEV
0
Atom feed of w3 alerts

Products

Latest w3 CVEs

Newest publication first

  1. HighCVSS 8.4 EPSS 0.39%

    There is a XXE in W3CSS Validator versions before cssval-20250226 that allows an attacker to use specially-crafted XML objects to coerce server-side request forgery (SSRF). This could be exploited to read arbitrary local files if an attacker has access to exception messages.

  2. MediumCVSS 6.1 EPSS 0.48%

    A vulnerability was found in w3c online-spellchecker-py up to 20140130. It has been rated as problematic. This issue affects some unknown processing of the file spellchecker. The manipulation leads to cross site scripting. The attack may be initiated remotely. The complexity of a...

  3. LowCVSS 3.7 EPSS 1.7%

    The W3C High Resolution Time API, as implemented in various web browsers, does not consider that memory-reference times can be measured by a performance.now "Time to Tick" approach even with the https://bugzilla.mozilla.org/show_bug.cgi?id=1167489#c9 protection mechanism in place...

  4. HighCVSS 10.0 EPSS 62.5% Framework module Public exploit PoC

    Multiple stack-based buffer overflows in W3C Amaya Web Browser 10.0 and 11.0 allow remote attackers to execute arbitrary code via (1) a long type parameter in an input tag, which is not properly handled by the EndOfXmlAttributeValue function; (2) an "HTML GI" in a start tag, whic...

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.