Skip to content

Vendor

SEOPress vulnerabilities

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

Total
14
Critical
1
High
3
Medium
10
Low
0
Unscored
0
CISA KEV
0
Atom feed of SEOPress alerts

Products

Latest SEOPress CVEs

Newest publication first

  1. MediumCVSS 6.1 EPSS 0.45%

    The SEOPress – On-site SEO plugin for WordPress is vulnerable to Reflected Cross-Site Scripting due to the use of add_query_arg & remove_query_arg without appropriate escaping on the URL in all versions up to, and including, 8.1.1. This makes it possible for unauthenticated attac...

  2. CriticalCVSS 9.8 EPSS 3.7%

    The SEOPress WordPress plugin before 7.9 does not properly protect some of its REST API routes, which combined with another Object Injection vulnerability can allow unauthenticated attackers to unserialize malicious gadget chains, compromising the site if a suitable chain is pres...

  3. MediumCVSS 6.1 EPSS 0.33%

    The SEOPress WordPress plugin before 7.8 does not validate and escape one of its Post settings, which could allow contributor and above role to perform Open redirect attacks against any user viewing a malicious post

  4. MediumCVSS 5.0 EPSS 0.34%

    The SEOPress WordPress plugin before 7.8 does not sanitise and escape some of its Post settings, which could allow high privilege users such as contributor to perform Stored Cross-Site Scripting attacks.

  5. MediumCVSS 4.8 EPSS 0.40%

    The SEOPress WordPress plugin before 7.3 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Cross-Site Scripting attacks even when unfiltered_html is disallowed

  6. HighCVSS 7.2 EPSS 17.7%

    The SEOPress WordPress plugin before 6.5.0.3 unserializes user input provided via the settings, which could allow high-privilege users such as admin to perform PHP Object Injection when a suitable gadget is present.

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.