WP Meta SEO <= 4.4.6 - Admin+ Stored Cross-Site Scripting via breadcrumbs
Strategic Overview
- Status
- Patched in 4.4.7
- Affected Plugin
- WP Meta SEO
- Affected Version
<= 4.4.6- CVSS
- 5.5Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2022-1093
At a glance
CVE-2022-1093 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the WP Meta SEO WordPress plugin, affecting versions <= 4.4.6. It carries a CVSS score of 5.5 (reachable over the network; low attack complexity). The issue is fixed in version 4.4.7; sites on affected versions should update now. Disclosed May 2022, reported by Victor Pasman.
Vulnerability Overview
The WP Meta SEO WordPress plugin before 4.4.7 does not sanitise or escape the breadcrumb separator before outputting it to the page, allowing a high privilege user such as an administrator to inject arbitrary javascript into the page even when unfiltered html is disallowed.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in WP Meta SEO <= 4.4.6 takes a caller who can reach the endpoint. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For WP Meta SEO the fix is 4.4.7: builds <= 4.4.6 are affected, anything from 4.4.7 onward is not.
Remediation
Update to version 4.4.7, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to WP Meta SEO: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Meta SEO 4.4.7 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
- 7.2CVE-2026-9643: WP Meta SEO <= 4.5.18 Stored Cross-Site Scripting
CVE-2026-9643 - 7.2CVE-2023-6961: WP Meta SEO <= 4.5.12 Stored Cross-Site Scripting
CVE-2023-6961 - 6.4CVE-2024-45456: WP Meta SEO <= 4.5.13 Stored Cross-Site Scripting
CVE-2024-45456 - 4.4CVE-2024-45455: WP Meta SEO <= 4.5.13 Stored Cross-Site Scripting
CVE-2024-45455
Other vulnerabilities in WP Meta SEO
- 8.8CVE-2023-1381: WP Meta SEO <= 4.5.4 PHAR Deserialization
CVE-2023-1381 - 8.8CVE-2023-0875: WP Meta SEO <= 4.5.2 SQL Injection
CVE-2023-0875 - 8.8CVE-2022-30337: WP Meta SEO <= 4.4.8 CSRF to Settings Update
CVE-2022-30337 - 7.1CVE-2023-0876: WP Meta SEO Missing Authorization in 'startProcess'
CVE-2023-0876 - 6.4CVE-2026-11370: WP Meta SEO <= 4.5.18 Server-Side Request Forgery
CVE-2026-11370 - 5.4CVE-2023-1022: WP Meta SEO Missing Authorization
CVE-2023-1022 - 5.4CVE-2023-1023: WP Meta SEO Missing Authorization
CVE-2023-1023 - 5.3CVE-2023-6962: WP Meta SEO <= 4.5.12 Information Exposure
CVE-2023-6962
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C