AWSM Team <= 1.3.1 - Authenticated (Contributor+) Local File Inclusion
Strategic Overview
- Status
- Patched in 1.3.2
- Affected Plugin
- AWSM Team – Team Showcase Plugin
- Affected Version
<= 1.3.1- CVSS
- 8.8High
- Weakness type
- CWE-98 · Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')
- CVE
CVE-2024-37454
At a glance
CVE-2024-37454 is a high-severity Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in the AWSM Team WordPress plugin, affecting versions <= 1.3.1. 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 at Contributor level or above. The issue is fixed in version 1.3.2; sites on affected versions should update now. Disclosed July 2024, reported by João Pedro Soares de Alcântara.
Vulnerability Overview
The AWSM Team – Team Showcase Plugin plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.3.1. This makes it possible for authenticated attackers, with Contributor-level access and above, to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.
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-98: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')
AWSM Team <= 1.3.1 carries this weakness at safe, and reaching it takes an account at Contributor level or above. PHP file inclusion means a path used by include or require is built from request data, so the file that gets executed is under the caller's influence.
Including an attacker-influenced file executes its contents, which is why this class is routinely chained with an upload or log-poisoning step to reach code execution. For AWSM Team the fix is 1.3.2: builds <= 1.3.1 are affected, anything from 1.3.2 onward is not.
Remediation
Update to version 1.3.2, or a newer patched version
How does WordSec protect against this?
An attacker needs Contributor 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. 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: AWSM Team 1.3.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C