CVE-2021-25003

WPCargo <= 6.8.9 - Unauthenticated Remote Code Execution

2022-02-21 00:00
Krzysztof Zając

Strategic Overview

Status
Patched in 6.9.0
Affected Plugin
WPCargo Track & Trace
Affected Version
< 6.9.0
CVSS
9.8Critical
Weakness type
CWE-94 · Improper Control of Generation of Code ('Code Injection')
CVE
CVE-2021-25003
View all WPCargo Track & Trace vulnerabilities

At a glance

CVE-2021-25003 is a critical-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the WPCargo Track & Trace WordPress plugin, affecting versions < 6.9.0. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 6.9.0; sites on affected versions should update now. Disclosed February 2022, reported by Krzysztof Zając.

Vulnerability Overview

The WPCargo Track & Trace WordPress plugin before 6.9.0 contains a file which could allow unauthenticated attackers to write a PHP file anywhere on the web server, leading to RCE

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, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-94: Improper Control of Generation of Code ('Code Injection')

Reaching this weakness in WPCargo Track & Trace < 6.9.0 takes no account at all. Code injection means input from a request reaches a language construct that evaluates code, so the attacker's text is executed rather than treated as data.

The injected code runs with the web server's privileges, giving the attacker the same access to the database and filesystem as WordPress itself. For WPCargo Track & Trace the fix is 6.9.0: builds < 6.9.0 are affected, anything from 6.9.0 onward is not.

Remediation

Update to version 6.9.0, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: WPCargo Track & Trace 6.9.0 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Login Security

External References

https://www.cve.org/CVERecord?id=CVE-2021-25003https://www.wordfence.com/threat-intel/vulnerabilities/id/14a1b8af-bd32-4245-92d6-549cae68c626https://nvd.nist.gov/vuln/detail/CVE-2021-25003

Related records

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