WordPress security by component
SEOPress
Plugin description
SEOPress is a WordPress component with 5 published CVE records in this archive. The latest tracked vulnerability was published Oct 29, 2024; the highest CVE/CNA score is 6.4.
Plugin slug:
wp-seopressLatest vulnerability
CVE-2024-50454: SEOPress: A security weakness
SEOPress is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
| Safe version |
|
||
|---|---|---|---|
| Oct 29, 2024 |
CVE-2024-50454
SEOPress: A security weakness
SEOPress is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE5.3
NVDPending
|
| Oct 02, 2024 |
CVE-2024-9225
SEOPress – On-site SEO: Cross-site scripting
SEOPress – On-site SEO is affected by cross-site scripting. The vulnerable path is reachable without authentication. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE6.1
NVDPending
|
| Jun 20, 2024 |
CVE-2024-1168
SEOPress – On-site SEO: Cross-site scripting
SEOPress – On-site SEO is affected by cross-site scripting. Exploitation requires an authenticated WordPress account. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE6.4
NVD5.4
|
| May 06, 2024 |
CVE-2024-34383
SEOPress: A security weakness
SEOPress is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE5.3
NVDPending
|
| Aug 16, 2021 |
CVE-2021-34641
SEOPress: A security weakness
SEOPress is affected by a security weakness. Exploitation requires an authenticated WordPress account. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE6.4
NVD5.4
|