Wp Meta Seo
Approved changes feed: RSS · Atom
cpe:2.3:a:joomunited:wp_meta_seo:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Joomunited (ac4800e3-8d14-52d4-a07b-f57bf4934a04) |
|---|---|
| Product | Wp Meta Seo (129e555e-353f-512c-a875-651adfae960b) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from purl2cpe mapping
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/wp-plugins/wp-meta-seo |
purl2cpe | 2026-06-01 10:11:30.915514 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-9643 |
vulnerable | 2026-07-29 01:12:09.463037 |
WP Meta SEO <= 4.5.18 - Unauthenticated Stored Cross-Site Scripting via REQUEST_URI in 404 Logging
HIGH (7.2)
The WP Meta SEO plugin for WordPress is vulnerable to Unauthenticated Stored Cross-Site Scripting via the REQUEST_URI server variable in all versions up to, and including, 4.5.18. When the plugin's `wpmsTemplateRedirect()` hook detects a 404, it concatenates `$_SERVER['HTTP_HOST']` with the raw `$_SERVER['REQUEST_URI']` and inserts that value verbatim into the `wp_wpms_links.link_url` column via `$wpdb->insert()`. This makes it possible for unauthenticated attackers to inject arbitrary web scripts that execute whenever an administrator views the plugin's 404 & Redirects admin page (`/wp-admin/admin.php?page=metaseo_broken_link`).
Published: 2026-06-24T05:33:29.486Z
Updated: 2026-06-29T19:07:51.167Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-11370 |
vulnerable | 2026-07-29 00:23:30.997531 |
WP Meta SEO <= 4.5.18 - Authenticated (Contributor+) Server-Side Request Forgery via 'new_link' Parameter
MEDIUM (6.4)
The WP Meta SEO plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 4.5.18 via the 'new_link' parameter. This makes it possible for authenticated attackers, with contributor-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services. The HTTP response status from outbound requests is reflected back in the AJAX JSON response as status_code, providing an enumeration oracle usable for probing internal hosts and cloud metadata services.
Published: 2026-06-24T05:33:23.066Z
Updated: 2026-06-29T19:13:55.110Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-45456 |
vulnerable | 2026-06-08 06:48:06.289331 |
WordPress WP Meta SEO plugin <= 4.5.13 - Cross Site Scripting (XSS) vulnerability
MEDIUM (6.5)
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in JoomUnited WP Meta SEO wp-meta-seo allows Stored XSS.This issue affects WP Meta SEO: from n/a through <= 4.5.13.
Published: 2024-09-15T07:47:02.241Z
Updated: 2026-04-28T16:10:17.747Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-45455 |
vulnerable | 2026-06-08 06:48:06.287749 |
WordPress WP Meta SEO plugin <= 4.5.13 - Cross Site Scripting (XSS) vulnerability
MEDIUM (5.9)
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in JoomUnited WP Meta SEO wp-meta-seo allows Stored XSS.This issue affects WP Meta SEO: from n/a through <= 4.5.13.
Published: 2024-09-15T07:52:41.232Z
Updated: 2026-04-28T16:10:17.940Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-6962 |
vulnerable | 2026-06-08 06:21:56.480064 |
WP Meta SEO <= 4.5.12 - Information Exposure via Meta Description
MEDIUM (5.3)
The WP Meta SEO plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 4.5.12 via the meta description. This makes it possible for unauthenticated attackers to disclose potentially sensitive information via the meta description of password-protected posts.
Published: 2024-05-02T16:51:41.692Z
Updated: 2026-04-08T16:32:48.990Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-6961 |
vulnerable | 2026-06-08 06:21:56.477730 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-1029 |
vulnerable | 2026-06-08 05:52:33.661542 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-1028 |
vulnerable | 2026-06-08 05:52:33.661093 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-1027 |
vulnerable | 2026-06-08 05:52:33.660484 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-1026 |
vulnerable | 2026-06-08 05:52:33.659775 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-1024 |
vulnerable | 2026-06-08 05:52:33.655719 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-1023 |
vulnerable | 2026-06-08 05:52:33.655067 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-1022 |
vulnerable | 2026-06-08 05:52:33.654455 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.