CVE-2022-0701

Seo 301 Meta <= 1.9.1 - Stored Cross-Site Scripting

2022-02-21 00:00
fuzzyap1

Strategic Overview

Status
Unpatched
Affected Plugin
Seo 301 Meta
Affected Version
<= 1.9.1
CVSS
5.5Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2022-0701
View all Seo 301 Meta vulnerabilities

At a glance

CVE-2022-0701 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Seo 301 Meta WordPress plugin, affecting versions <= 1.9.1. It carries a CVSS score of 5.5 (reachable over the network; low attack complexity). No fixed release has been reported yet; treat installations running this software as exposed. Disclosed February 2022, reported by fuzzyap1.

Vulnerability Overview

The SEO 301 Meta WordPress plugin through 1.9.1 does not escape its Request and Destination settings, allowing high privilege users such as admin to perform Cross-Site Scripting attacks even when the unfiltered_html capability 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 Seo 301 Meta <= 1.9.1 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. No fixed build of this plugin is recorded for Seo 301 Meta yet, so installs running <= 1.9.1 stay exposed until the vendor ships one.

Remediation

No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.

How does WordSec protect against this?

The attempt arrives as an ordinary request to Seo 301 Meta: WordSec's web application firewall inspects request payloads before WordPress loads them. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.

  • Firewall
  • Alerts

External References

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C