dbcve.org
Counter BoxWordPress extension · Wow Company

CVE-2022-29446

HIGH · 7.2 CVSS v3.1 Published 2022-05-19
Fix available
A fix is available. Upgrade to after 1.1.1 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 Counter Box plugin <= 1.1.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 · high confidence

Local File Inclusion vulnerability in Wow-Company's Counter Box WordPress plugin (versions 1.1.1 and below) allows authenticated administrators or higher-privileged users to include and potentially read arbitrary files on the server through unsanitized input parameters.

MitigationUpdate the Counter Box plugin to the latest version (1.1.2 or later) which includes proper input validation to prevent path traversal. If immediate update is not possible, restrict administrator role access and monitor for suspicious file inclusion attempts.

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
Counter BoxWordPress extension
Affected:<= 1.1.1

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. Confirm Counter Box plugin installation
    Navigate to WordPress admin > Plugins and locate 'Counter Box' by Wow Company in the installed plugins list
    Affected if The plugin is installed and active in WordPress
  2. Determine installed plugin version
    In Plugins list, click on the plugin details or check the plugin's main PHP file header for the Version field. Alternatively, compare against the WordPress plugin repository version listing
    Affected if Version is 1.1.1 or lower (the vulnerable version range)
  3. Identify administrator-level users
    Check WordPress user management for accounts with Administrator role. The vulnerability requires authenticated administrators or higher-privileged users
    Affected if Administrator or super-admin accounts exist on the WordPress site
  4. Locate the file inclusion parameter
    Review plugin PHP source code for file inclusion functions (include, require, include_once, require_once) that accept user-supplied input without sanitization. Look for parameters handling file paths
    Affected if Code contains unsanitized file inclusion logic processing user input from request parameters

You are affected if the Counter Box plugin is installed at version 1.1.1 or below and your site has administrator accounts, as the vulnerability requires both the vulnerable plugin version and authenticated admin-level access to exploit the path traversal in file inclusion parameters.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 1.1.1
Interim mitigation

Update the Counter Box plugin to the latest version (1.1.2 or later) which includes proper input validation to prevent path traversal. If immediate update is not possible, restrict administrator role access and monitor for suspicious file inclusion attempts.

Recommended fix Moderate confidence

1.1.2 or latest available version

  1. Create a full backup of your WordPress site and database before making any changes
  2. Log in to WordPress admin with administrator privileges
  3. Navigate to Plugins > Installed Plugins
  4. Find the Counter Box plugin and check if an update is available
  5. If an update is available, click 'Update Now' to install the latest version
  6. If no automatic update is available, manually download the latest version from wordpress.org/plugins/counter-box and upload it via Plugins > Add New > Upload Plugin
  7. After updating, verify the plugin is active and functioning correctly
  8. Review user roles and remove any unnecessary administrator accounts to follow principle of least privilege
Caveat No known breaking changes reported for this security update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Counter Box Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-29446 — 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-29446 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