dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-7359

HIGH · 8.2 CVSS v3.1 Published 2025-07-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable No privileges 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
The Counter live visitors for WooCommerce plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the wcvisitor_get_block function in all versions up to, and including, 1.3.6. This makes it possible for unauthenticated attackers to delete arbitrary files on the server. NOTE: This particular vulnerability deletes all the files in a targeted arbitrary directory rather than a specified arbitrary file, which can lead to loss of data or a denial of service condition.

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

The Counter live visitors for WooCommerce WordPress plugin versions up to 1.3.6 lack proper file path validation in the wcvisitor_get_block function, allowing unauthenticated attackers to delete all files within arbitrary server directories. This results from insufficient input sanitization enabling path traversal-like behavior.

MitigationUpdate the plugin to the latest version immediately. If no patch is available, consider removing the plugin or disabling the affected function via .htaccess or firewall rules until a fix is released. Assess logs for any suspicious deletion activity.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L

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 plugin installation
    Check if the 'counter-live-visitors-for-woocommerce' plugin exists in the WordPress plugins directory at wp-content/plugins/. Look for a folder named 'counter-live-visitors-for-woocommerce' or similar.
    Affected if The plugin folder exists in the WordPress installation.
  2. Identify installed version
    Open the main plugin file (usually counter-live-visitors-for-woocommerce.php or index.php inside the plugin folder) and locate the version comment or the 'Version:' header in the plugin metadata. Compare this version number to the affected range: versions up to and including 1.3.6 are vulnerable.
    Affected if The installed version is 1.3.6 or lower.
  3. Verify vulnerable function accessibility
    Check if the wcvisitor_get_block function is registered as an AJAX handler accessible to unauthenticated users. Look in the plugin code for add_action('wp_ajax_wcvisitor_get_block', ...) or add_action('wp_ajax_nopriv_wcvisitor_get_block', ...). The presence of 'wp_ajax_nopriv_' indicates unauthenticated access is possible.
    Affected if The function is hooked to wp_ajax_nopriv_wcvisitor_get_block, allowing unauthenticated access.
  4. Review access controls on the affected endpoint
    Examine the wcvisitor_get_block function implementation to confirm it lacks capability checks (like current_user_can) or nonce validation. Search the function code for 'current_user_can' or 'wp_verify_nonce'.
    Affected if No capability checks or nonce validation exist in the wcvisitor_get_block function.
  5. Inspect server logs for deletion attempts
    Search WordPress debug logs, Apache/nginx access logs, or server error logs for requests containing 'wcvisitor_get_block' combined with path traversal patterns (such as '../' or absolute paths in the request parameters).
    Affected if Log entries show requests to wcvisitor_get_block with directory traversal patterns or unusual file deletion activity.

A user is affected if the Counter live visitors for WooCommerce plugin version 1.3.6 or lower is installed and the wcvisitor_get_block function is accessible to unauthenticated users without proper validation.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to the latest version immediately. If no patch is available, consider removing the plugin or disabling the affected function via .htaccess or firewall rules until a fix is released. Assess logs for any suspicious deletion activity.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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