CVE-2022-29446

Counter Box <= 1.1.1 - Authenticated Local File Inclusion

2022-05-16 13:55
0xB9

Strategic Overview

Status
Patched in 1.2
Affected Version
<= 1.1.1
CVSS
6.8Medium
Weakness type
CWE-98 · Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')
CVE
CVE-2022-29446
View all Counter Box – Add Countdowns, Timers & Dynamic Counters to WordPress vulnerabilities

At a glance

CVE-2022-29446 is a medium-severity Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in the Counter Box WordPress plugin, affecting versions <= 1.1.1. It carries a CVSS score of 6.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account. The issue is fixed in version 1.2; sites on affected versions should update now. Disclosed May 2022, reported by 0xB9.

Vulnerability Overview

Authenticated (administrator or higher role) Local File Inclusion (LFI) vulnerability in Wow-Company's Counter Box plugin <= 1.1.1 at WordPress.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed. 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 Counter Box <= 1.1.1 takes any authenticated account. 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 Counter Box the fix is 1.2: builds <= 1.1.1 are affected, anything from 1.2 onward is not.

Remediation

Update to version 1.2, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Counter Box: 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: Counter Box 1.2 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