CVE-2022-0674

Kunze Law < 2.1 - Authenticated (Admin+) Stored Cross-Site Scripting

2022-02-17 00:00
fuzzyap1

Strategic Overview

Status
Patched in 2.1
Affected Plugin
Kunze Law
Affected Version
< 2.1
CVSS
5.5Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2022-0674
View all Kunze Law vulnerabilities

At a glance

CVE-2022-0674 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Kunze Law WordPress plugin, affecting versions < 2.1. It carries a CVSS score of 5.5 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Admin level or above. The issue is fixed in version 2.1; sites on affected versions should update now. Disclosed February 2022, reported by fuzzyap1.

Vulnerability Overview

The Kunze Law WordPress plugin before 2.1 does not escape its 'E-Mail Error "From" Address' 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')

Kunze Law < 2.1 carries this weakness at From, and reaching it takes an account at Admin level or above. 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 Kunze Law the fix is 2.1: builds < 2.1 are affected, anything from 2.1 onward is not.

Remediation

Update to version 2.1, or a newer patched version

How does WordSec protect against this?

An attacker needs Admin access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Kunze Law 2.1 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

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