dbcve.org
Popup BoxWordPress extension · Wow Estore

CVE-2022-29445

HIGH · 7.2 CVSS v3.1 Published 2022-05-18
Fix available
A fix is available. Upgrade to after 2.1.2 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
Authenticated (administrator or higher role) Local File Inclusion (LFI) vulnerability in Wow-Company's Popup Box plugin <= 2.1.2 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 · high confidence

Authenticated Local File Inclusion (LFI) vulnerability in Wow-Company's Popup Box plugin for WordPress (versions <= 2.1.2) allows an attacker with administrator-level privileges to read arbitrary files on the server by manipulating file path parameters.

MitigationUpdate the Wow-Company Popup Box plugin to the latest version (or remove the plugin if no update is available) and review server file permissions to limit exposure.

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
Popup BoxWordPress extension
Affected:<= 2.1.2

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify if Wow Estore Popup Box plugin is installed
    Access WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Wow Estore Popup Box' or 'Popup Box' by Wow-Company in the list of active plugins.
    Affected if The plugin is present in the WordPress installation regardless of activation status
  2. Determine installed plugin version
    In the plugins list, click on the plugin name or view the plugin files. Check the main plugin PHP file (usually popup-box.php or similar) for the Version header in the plugin comment block, or check the readme.txt file for the Stable tag.
    Affected if The installed version is 2.1.2 or any version lower than 2.1.2
  3. Identify vulnerable file parameter
    Examine the plugin PHP files for functions handling file path parameters, typically involving 'file_get_contents', 'readfile', 'include', or 'require' where user input directly influences the file path without proper sanitization.
    Affected if The plugin code contains file read operations that accept path parameters without validation, common patterns include $_GET or $_POST parameters used in file inclusion functions
  4. Check for admin-level user access
    Review WordPress user roles under Users > All Users in the admin panel. Identify accounts with Administrator role level.
    Affected if Any WordPress user account with Administrator privileges exists in the system, as this CVE requires admin-level authentication to exploit
  5. Inspect server access logs for LFI attempts
    Review web server access logs (Apache/nginx) for suspicious requests to wp-admin/admin-ajax.php or plugin endpoints containing path traversal patterns like '..' or direct file references such as '/etc/passwd' or 'wp-config.php'.
    Affected if Log entries show requests with path traversal patterns targeting the Popup Box plugin endpoints

A user is affected if the Wow Estore Popup Box plugin version 2.1.2 or lower is installed AND the vulnerable file path parameter code exists in the plugin AND an administrator-level user account is present in WordPress.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 2.1.2
Interim mitigation

Update the Wow-Company Popup Box plugin to the latest version (or remove the plugin if no update is available) and review server file permissions to limit exposure.

Fix this in Popup Box Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-29445 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-29445 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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