The Simple SEO WordPress plugin before 2.0.32 does not sanitise and escape some parameters when outputing them in the page, which could allow users with a role as low as contributor to perform Cross-Site Scripting attacks.
Product
wordpress cds-simple-seo vulnerabilities
6 published CVES affecting wordpress cds-simple-seo, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 6
- Critical
- 0
- High
- 0
- Medium
- 6
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest wordpress cds-simple-seo CVEs
Newest publication first
-
MediumCVSS 6.1 EPSS 0.19%
-
MediumCVSS 5.4 EPSS 0.22%
Cross-Site Request Forgery (CSRF) vulnerability in David Cole Simple SEO plugin <= 2.0.25 versions.
-
MediumCVSS 5.4 EPSS 0.31%
Cross-Site Request Forgery (CSRF) vulnerability in David Cole Simple SEO plugin <= 1.8.12 on WordPress allows attackers to create or delete sitemaps.
-
CVE-2022-36404 WordPress Simple SEO plugin <= 1.8.12 - Broken Access Control vulnerability
PublishedMediumCVSS 5.4 EPSS 0.26%Missing Authorization, Cross-Site Request Forgery (CSRF) vulnerability in David Cole Simple SEO (WordPress plugin) plugin <= 1.8.12 versions.
-
CVE-2022-1628 Simple SEO <= 1.7.91 - Authenticated (Contributor+) Stored Cross-Site Scripting
PublishedMediumCVSS 5.4 EPSS 0.63%The Simple SEO plugin for WordPress is vulnerable to attribute-based stored Cross-Site Scripting in versions up to, and including 1.7.91, due to insufficient sanitization or escaping on the SEO social and standard title parameters. This can be exploited by authenticated users wit...
-
WORDFENCE-9a83f381-a8ce-472d-a202-f7d7f22fd650 Simple SEO <= 1.7.91 - Reflected Cross-Site Scripting
PublishedMediumCVSS 6.1The Simple SEO plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the ‘s’ parameter in versions up to, and including, 1.7.91 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary...
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.