Skip to content

Product

wordpress super-socializer vulnerabilities

13 published CVES affecting wordpress super-socializer, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
13
Critical
1
High
3
Medium
9
Low
0
Unscored
0
CISA KEV
0

Latest wordpress super-socializer CVEs

Newest publication first

  1. MediumCVSS 5.3 EPSS 0.45%

    The Social Share, Social Login and Social Comments Plugin – Super Socializer plugin for WordPress is vulnerable to Limited SQL Injection via the ‘SuperSocializerKey’ parameter in all versions up to, and including, 7.14 due to insufficient escaping on the user supplied parameter a...

  2. MediumCVSS 4.8 EPSS 0.50%

    The Social Share, Social Login and Social Comments Plugin WordPress plugin before 7.13.64 does not sanitise and escape some of its settings, which could allow high privilege users such as editors to perform Cross-Site Scripting attacks even when unfiltered_html is disallowed

  3. MediumCVSS 6.1 EPSS 6.0% Public exploit Scanner template

    The Social Share, Social Login and Social Comments WordPress plugin before 7.13.52 does not sanitise and escape a parameter before outputting it back in the page, leading to a Reflected Cross-Site Scripting which could be used against high privilege users such as admin.

  4. MediumCVSS 5.4 EPSS 0.50%

    The Social Share, Social Login and Social Comments Plugin WordPress plugin before 7.13.44 does not validate and escape some of its shortcode attributes before outputting them back in the page, which could allow users with a role as low as contributor to perform Stored Cross-Site...

  5. MediumCVSS 6.1 EPSS 1.9% Scanner template

    The Social Share, Social Login and Social Comments Plugin WordPress plugin before 7.13.30 does not sanitise and escape the urls parameter in its the_champ_sharing_count AJAX action (available to both unauthenticated and authenticated users) before outputting it back in the respon...

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.