Skip to content

Technology

WordPress vulnerabilities

WordPress core, plugins and themes. 44,626 published CVES affecting WordPress, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
44,626
Critical
3,732
High
13,190
Medium
27,095
Low
505
Unscored
104
CISA KEV
9
Atom feed of WordPress alerts

Latest WordPress CVEs

Newest publication first · page 13 of 40 · showing the latest 1,000

  1. MediumCVSS 6.8 EPSS 0.40%

    The Elementor Website Builder WordPress plugin before 4.3.6 does not validate or escape an element identifier before rendering it into a client-side framework attribute that is evaluated as JavaScript, allowing users with the Contributor role to store scripts that execute in the...

  2. LowCVSS 3.5 EPSS 0.24%

    The Live Composer WordPress plugin before 2.1.24 does not sanitise and escape some of its Button module settings before outputting them on the front end, which could allow high-privilege users such as administrators to perform Stored Cross-Site Scripting attacks even when the unf...

  3. LowCVSS 3.5 EPSS 0.23%

    The Live Composer WordPress plugin before 2.1.24 does not sanitise and escape some of its page-builder module settings before outputting them, allowing users with access to the builder (Administrator by default) to inject arbitrary JavaScript that executes when the affected page...

  4. LowCVSS 3.5 EPSS 0.24%

    The Live Composer WordPress plugin before 2.1.24 does not sanitise and escape some of its staff member settings before outputting them in pages, which could allow high-privilege users such as administrators to perform Stored Cross-Site Scripting attacks even when the unfiltered_h...

  5. LowCVSS 3.5 EPSS 0.24%

    The Live Composer WordPress plugin before 2.1.24 does not sanitise and escape some of its module settings before outputting them in an href attribute, which could allow high-privilege users such as administrators to perform Stored Cross-Site Scripting attacks even when the unfilt...

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.