CVE-2021-24347

SP Project & Document Manager <= 4.21 - Authenticated Shell Upload

2021-05-25 00:00
Viktor Markopoulos

Strategic Overview

Status
Patched in 4.22
Affected Plugin
SP Project & Document Manager
Affected Version
< 4.22
CVSS
8.8High
Weakness type
CWE-94 · Improper Control of Generation of Code ('Code Injection')
CVE
CVE-2021-24347
View all SP Project & Document Manager vulnerabilities

At a glance

CVE-2021-24347 is a high-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the SP Project & Document Manager WordPress plugin, affecting versions < 4.22. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account. The issue is fixed in version 4.22; sites on affected versions should update now. Disclosed May 2021, reported by Viktor Markopoulos.

Vulnerability Overview

The SP Project & Document Manager WordPress plugin before 4.22 allows users to upload files, however, the plugin attempts to prevent php and other similar files that could be executed on the server from being uploaded by checking the file extension. It was discovered that php files could still be uploaded by changing the file extension's case, for example, from "php" to "pHP".

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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

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

SP Project & Document Manager < 4.22 carries this weakness at php, and reaching it takes any authenticated account. 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 SP Project & Document Manager the fix is 4.22: builds < 4.22 are affected, anything from 4.22 onward is not.

Remediation

Update to version 4.22, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to SP Project & Document Manager: 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: SP Project & Document Manager 4.22 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2021-24347https://www.wordfence.com/threat-intel/vulnerabilities/id/1f81d9f2-f7a1-4085-aa20-d991cecacd23https://nvd.nist.gov/vuln/detail/CVE-2021-24347

Related records

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