CVE-2022-30545

5 Anker Connect <= 1.2.6 - Reflected Cross-Site Scripting

2022-10-12 00:00
ptsfence

Strategic Overview

Status
Patched in 1.2.7
Affected Plugin
5 Anker Connect
Affected Version
<= 1.2.6
CVSS
6.1Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2022-30545
View all 5 Anker Connect vulnerabilities

At a glance

CVE-2022-30545 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the 5 Anker Connect WordPress plugin, affecting versions <= 1.2.6. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.2.7; sites on affected versions should update now. Disclosed October 2022, reported by ptsfence.

Vulnerability Overview

The 5 Anker Connect plugin for WordPress is vulnerable to Reflected Cross-Site Scripting in versions up to, and including, 1.2.6 due to insufficient input sanitization and output escaping on the 'tab' parameter. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.

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 privileges on the target site.

CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

5 Anker Connect <= 1.2.6 carries this weakness at tab, and reaching it 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 5 Anker Connect the fix is 1.2.7: builds <= 1.2.6 are affected, anything from 1.2.7 onward is not.

Remediation

Update to version 1.2.7, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to 5 Anker Connect: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: 5 Anker Connect 1.2.7 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

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