Hover EffectsWordPress extension · Wow Company
CVE-2022-29447
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAuthenticated (administrator or higher user role) Local File Inclusion (LFI) vulnerability in Wow-Company's Hover Effects plugin <= 2.1 at WordPress.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceAuthenticated Local File Inclusion vulnerability in Wow-Company's Hover Effects WordPress plugin (versions 2.1 and below) allows administrator-level users to read sensitive files on the server through insecure file path handling in plugin parameters.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Hover EffectsWordPress extension
<= 2.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Hover Effects plugin is installedIn WordPress admin, navigate to Plugins > Installed Plugins and look for 'Hover Effects' by Wow Company, or check the /wp-content/plugins/ directory for a folder named 'hover-effects' or similar Wow Company plugin folderAffected if The plugin is present in the WordPress installation
-
Determine installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins > Hover Effects and view the version number displayed, or read the main plugin PHP file header for the Version fieldAffected if Version is 2.1 or lower, or if the version field cannot be determined (indicating outdated or unmaintained plugin)
-
Confirm admin-level user accounts existNavigate to WordPress Users panel and check for users with Administrator role, or query the wp_users and wp_usermeta tables for users with wp_capabilities containing 'administrator'Affected if Any administrator-level user account exists in the WordPress installation (required for exploiting this authenticated LFI)
-
Inspect plugin source for vulnerable file inclusion patternsExamine the main plugin PHP files (typically in wp-content/plugins/hover-effects/ or similar) for functions using include, require, or similar that incorporate request parameters without sanitization, particularly file path parametersAffected if The plugin code uses unsanitized input from $_GET, $_POST, or similar superglobals in file inclusion functions
The environment is affected if the Hover Effects plugin version 2.1 or lower is installed, the plugin contains vulnerable file inclusion code, and an administrator account exists to trigger the LFI flaw.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate Hover Effects plugin to version newer than 2.1; if no patched version available, remove or disable the plugin and implement web application firewall rules to detect LFI patterns in request parameters.
Fix this in Hover Effects
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29447 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-29447 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data