WordPress security by component
WP Meta SEO
Plugin description
WP Meta SEO is a WordPress component with 18 published CVE records in this archive. The latest tracked vulnerability was published Jun 24, 2026; the highest CVE/CNA score is 8.8.
Plugin slug:
wp-meta-seoLatest vulnerability
CVE-2026-9643: WP Meta SEO: Cross-site scripting
WP Meta 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. The published affected range is <= 4.5.18.
| Safe version |
|
||
|---|---|---|---|
| Jun 24, 2026 |
CVE-2026-9643
WP Meta SEO: Cross-site scripting
WP Meta 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. The published affected range is <= 4.5.18.
|
> 4.5.18 |
CVE7.2
NVDPending
|
| Jun 24, 2026 |
CVE-2026-11370
WP Meta SEO: Server-side request forgery
WP Meta SEO is affected by server-side request forgery. Exploitation requires at least contributor-level access. The vulnerable server can be induced to make attacker-selected network requests. The published affected range is <= 4.5.18.
|
> 4.5.18 |
CVE6.4
NVDPending
|
| Sep 15, 2024 |
CVE-2024-45456
WP Meta SEO: Cross-site scripting
WP Meta SEO is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE6.5
NVD5.4
|
| Sep 15, 2024 |
CVE-2024-45455
WP Meta SEO: Cross-site scripting
WP Meta SEO is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE5.9
NVD4.8
|
| May 02, 2024 |
CVE-2023-6962
WP Meta SEO: Sensitive information exposure
WP Meta SEO is affected by sensitive information exposure. The vulnerable path is reachable without authentication. Successful exploitation can disclose data that should not be available to the caller.
|
See mitigation notes |
CVE5.3
NVDPending
|
| May 02, 2024 |
CVE-2023-6961
WP Meta SEO: Cross-site scripting
WP Meta 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 |
CVE7.2
NVD6.1
|
| Apr 10, 2023 |
CVE-2023-1381
WP Meta SEO: Code execution
WP Meta SEO is affected by code execution. Exposure depends on how the affected operation is made reachable by the site. Successful exploitation can run attacker-controlled code in the WordPress hosting account.
|
See mitigation notes |
CVE8.8
NVD8.8
|
| Mar 20, 2023 |
CVE-2023-0876
WP Meta SEO: A security weakness
WP Meta SEO 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 |
CVE6.1
NVD6.1
|
| Mar 20, 2023 |
CVE-2023-0875
WP Meta SEO: SQL injection
WP Meta SEO is affected by SQL injection. Exposure depends on how the affected operation is made reachable by the site. A successful request can alter database queries and expose or modify WordPress data.
|
See mitigation notes |
CVE8.8
NVD8.8
|
| Feb 28, 2023 |
CVE-2023-1028
WP Meta SEO: Cross-site request forgery
WP Meta SEO is affected by cross-site request forgery. The vulnerable path is reachable without authentication. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.
|
See mitigation notes |
CVE4.3
NVD4.3
|
| Feb 28, 2023 |
CVE-2023-1027
WP Meta SEO: A security weakness
WP Meta SEO is affected by a security weakness. Exploitation requires at least subscriber-level access. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE4.3
NVD4.3
|
| Feb 28, 2023 |
CVE-2023-1026
WP Meta SEO: A security weakness
WP Meta SEO is affected by a security weakness. Exploitation requires at least subscriber-level access. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE4.3
NVD4.3
|
| Feb 28, 2023 |
CVE-2023-1024
WP Meta SEO: A security weakness
WP Meta SEO is affected by a security weakness. Exploitation requires at least subscriber-level access. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE4.3
NVD4.3
|
| Feb 28, 2023 |
CVE-2023-1023
WP Meta SEO: A security weakness
WP Meta SEO is affected by a security weakness. Exploitation requires at least subscriber-level access. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE5.4
NVD4.3
|
| Feb 28, 2023 |
CVE-2023-1022
WP Meta SEO: A security weakness
WP Meta SEO is affected by a security weakness. Exploitation requires at least subscriber-level access. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE5.4
NVD4.3
|
| Feb 24, 2023 |
CVE-2023-1029
WP Meta SEO: Cross-site request forgery
WP Meta SEO is affected by cross-site request forgery. The vulnerable path is reachable without authentication. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.
|
See mitigation notes |
CVE4.3
NVD4.3
|
| Jul 21, 2022 |
CVE-2022-30337
Wp Meta Seo: Cross-site request forgery
Wp Meta Seo is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.
|
See mitigation notes |
CVE5.4
NVD4.3
|
| May 23, 2022 |
CVE-2022-1093
WP Meta SEO: A security weakness
WP Meta SEO 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 |
CVE4.8
NVD4.8
|