dbcve.org
Wolf Wordpress Posts Bulk Editor And Products Manager ProfessionalWordPress extension · Pluginus

CVE-2024-52396

HIGH · 8.8 CVSS v3.1 Published 2024-11-14
Fix available
A fix is available. Upgrade to 1.0.8.4 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in RealMag777 WOLF bulk-editor allows Path Traversal.This issue affects WOLF: from n/a through <= 1.0.8.3.

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 confidence

Path traversal vulnerability in RealMag777 WOLF bulk-editor plugin allows attackers to access files outside restricted directories using '../' sequences in file path parameters. This could enable unauthorized file读取 or potentially remote code execution depending on accessible system files.

MitigationUpdate WOLF bulk-editor to the latest patched version once available. Until then, restrict file access via web server configuration, disable the plugin if not essential, and implement strict input validation on all file path 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
Wolf Wordpress Posts Bulk Editor And Products Manager ProfessionalWordPress extension
Affected:< 1.0.8.4

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

CVSS:3.1/AV:N/AC:L/PR:L/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 WOLF plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'WOLF | WordPress Posts Bulk Editor And Products Manager Professional' or similar WOLF plugin entry in the list.
    Affected if Plugin is present and active in the WordPress installation
  2. Check installed plugin version
    In the Plugins list, locate the WOLF plugin entry and note the version number displayed below the plugin name. Compare against the affected range: versions prior to 1.0.8.4 are vulnerable.
    Affected if Installed version is less than 1.0.8.4
  3. Verify file management features are accessible
    Check if the plugin's file browser, import/export, or file handling modules are enabled. Look for settings under the plugin's menu (often labeled 'WOLF', 'Bulk Editor', or 'Products Manager') and confirm if file upload, CSV import, or template features are active.
    Affected if File handling modules are enabled and accessible to users
  4. Inspect web server access logs for path traversal patterns
    Search access logs (typically in /var/log/nginx/access.log or /var/log/apache2/access.log) for requests containing '../' sequences targeting the WOLF plugin endpoint, such as 'wp-admin/admin-ajax.php' with path traversal patterns in parameters.
    Affected if Log entries show '../' sequences in requests to WOLF plugin AJAX handlers or file processing endpoints

A WordPress site is affected if the WOLF bulk-editor plugin is installed with a version prior to 1.0.8.4 and the plugin's file handling features are accessible.

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 1.0.8.4 or later
Fixed in 1.0.8.4
Interim mitigation

Update WOLF bulk-editor to the latest patched version once available. Until then, restrict file access via web server configuration, disable the plugin if not essential, and implement strict input validation on all file path parameters.

Recommended fix Moderate confidence

1.0.8.4

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'WOLF - Wordpress Posts Bulk Editor And Products Manager Professional' plugin
  4. 4. If an update is available, click 'Update Now' to update to version 1.0.8.4
  5. 5. Alternatively, navigate to Plugins > Add New > Upload Plugin and upload version 1.0.8.4 of the plugin
  6. 6. After updating, verify the plugin version shows 1.0.8.4

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

Fix this in Wolf Wordpress Posts Bulk Editor And Products Manager Professional Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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