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

CVE-2025-24605

HIGH · 7.2 CVSS v3.1 Published 2025-02-03
Fix available
A fix is available. Upgrade to 1.0.8.6 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
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.5.

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

The WOLF bulk-editor plugin for WordPress contains a path traversal vulnerability (CWE-22) that allows attackers to use '../' sequences in file path parameters to access files outside the intended restricted directory. This improper limitation of pathname to a restricted directory could allow unauthorized file access or disclosure.

MitigationUpdate to the latest version of WOLF bulk-editor if a patch is available, or implement proper input validation that canonicalizes paths and restricts file access to only allowed directories using realpath() checks and whitelist-based validation.

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.6

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 WOLF bulk-editor plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'WOLF bulk-editor' or 'Pluginus Wolf Wordpress Posts Bulk Editor And Products Manager Professional' in the plugin list
    Affected if The plugin appears in the installed plugins list
  2. Identify the installed plugin version
    Click on the plugin name/details in the WordPress plugins page to view the installed version number, or inspect the plugin's main PHP file (usually named similarly to the plugin slug) for the 'Version' header in the plugin comment block
    Affected if The displayed version number is lower than 1.0.8.6
  3. Check for vulnerable file operation features
    Look for plugin settings or admin pages related to file import, export, upload, or file path handling. These are typically found under the plugin's menu in the WordPress admin sidebar
    Affected if The plugin provides any functionality that accepts file path parameters and the installed version is below 1.0.8.6
  4. Confirm the path traversal vulnerability condition
    The vulnerability exists when the plugin processes file paths without proper sanitization using realpath() checks. If the plugin is installed and version is below 1.0.8.6, the path traversal risk is present regardless of specific feature usage
    Affected if Installed plugin version is below 1.0.8.6

If the WOLF bulk-editor plugin is installed with a version number lower than 1.0.8.6, the environment is affected by this path traversal vulnerability.

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.6 or later
Fixed in 1.0.8.6
Interim mitigation

Update to the latest version of WOLF bulk-editor if a patch is available, or implement proper input validation that canonicalizes paths and restricts file access to only allowed directories using realpath() checks and whitelist-based validation.

Recommended fix High confidence

WOLF plugin version 1.0.8.6

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'WOLF - Wordpress Posts Bulk Editor And Products Manager Professional' plugin
  4. Click 'Update Now' if an update is available, or manually upload version 1.0.8.6
  5. Verify the update completed successfully
  6. Test the plugin functionality to ensure proper operation

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
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
17.0 hours of engineering $3,020
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,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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