Hover Effects – easily create any hover effect <= 2.1 - Authenticated Local File Inclusion
Strategic Overview
- Status
- Patched in 2.1.1
- Affected Plugin
- Hover Effects – easily create any hover effect
- Affected Version
<= 2.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-29447
At a glance
CVE-2022-29447 is a medium-severity Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in the Hover Effects WordPress plugin, affecting versions <= 2.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 2.1.1; sites on affected versions should update now. Disclosed May 2022, reported by 0xB9.
Vulnerability Overview
Authenticated (administrator or higher user role) Local File Inclusion (LFI) vulnerability in Wow-Company's Hover Effects plugin <= 2.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 Hover Effects <= 2.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 Hover Effects the fix is 2.1.1: builds <= 2.1 are affected, anything from 2.1.1 onward is not.
Remediation
Update to version 2.1.1, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Hover Effects: 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: Hover Effects 2.1.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Related records
Other vulnerabilities in Hover Effects – easily create any hover effect
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C