CVE-2021-24970

All-In-One-Gallery <= 2.4.9 - Admin+ Local File Inclusion

2021-11-15 00:00
Mohamed Magdy AbuMuslim

Strategic Overview

Status
Patched in 2.5.0
Affected Version
<= 2.4.9
CVSS
7.2High
Weakness type
CWE-98 · Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')
CVE
CVE-2021-24970
View all All-in-One Video Gallery – Video Player & Galleries for YouTube, Vimeo & Self-Hosted Videos vulnerabilities

At a glance

CVE-2021-24970 is a high-severity Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in the All-in-One Video Gallery WordPress plugin, affecting versions <= 2.4.9. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 2.5.0; sites on affected versions should update now. Disclosed November 2021, reported by Mohamed Magdy AbuMuslim.

Vulnerability Overview

The All-in-One Video Gallery WordPress plugin before 2.5.0 does not sanitise and validate the tab parameter before using it in a require statement in the admin dashboard, leading to a Local File Inclusion issue

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

Reaching this weakness in All-in-One Video Gallery <= 2.4.9 takes a caller who can reach the endpoint. 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 All-in-One Video Gallery the fix is 2.5.0: builds <= 2.4.9 are affected, anything from 2.5.0 onward is not.

Remediation

Update to version 2.5.0, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to All-in-One Video Gallery: 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: All-in-One Video Gallery 2.5.0 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

Related records

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