CVE-2022-1436

WPCargo Track & Trace <= 6.9.4 - Reflected Cross-Site Scripting

2022-04-25 00:00
Raul

Strategic Overview

Status
Patched in 6.9.5
Affected Plugin
WPCargo Track & Trace
Affected Version
<= 6.9.4
CVSS
6.1Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2022-1436
View all WPCargo Track & Trace vulnerabilities

At a glance

CVE-2022-1436 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the WPCargo Track & Trace WordPress plugin, affecting versions <= 6.9.4. 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 6.9.5; sites on affected versions should update now. Disclosed April 2022, reported by Raul.

Vulnerability Overview

The WPCargo Track & Trace WordPress plugin before 6.9.5 does not sanitise and escape the wpcargo_tracking_number parameter before outputting it back in the page, which could allow attackers to perform reflected Cross-Site Scripting attacks.

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')

Reaching this weakness in WPCargo Track & Trace <= 6.9.4 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 WPCargo Track & Trace the fix is 6.9.5: builds <= 6.9.4 are affected, anything from 6.9.5 onward is not.

Remediation

Update to version 6.9.5, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WPCargo Track & Trace: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WPCargo Track & Trace 6.9.5 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