dbcve.org
Bear Woocommerce Bulk Editor And Products Manager ProfessionalWordPress extension · Pluginus

CVE-2024-31430

HIGH · 8.8 CVSS v3.1 Published 2024-04-10
Fix available
A fix is available. Upgrade to 1.0.8.2 / 1.1.4.2 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in realmag777 WOLF – WordPress Posts Bulk Editor and Manager Professional, realmag777 BEAR – Bulk Editor and Products Manager Professional for WooCommerce by Pluginus.Net.This issue affects WOLF – WordPress Posts Bulk Editor and Manager Professional: from n/a through 1.0.8.1; BEAR – Bulk Editor and Products Manager Professional for WooCommerce by Pluginus.Net: from n/a through 1.1.4.1.

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

Cross-Site Request Forgery (CSRF) vulnerability in two WordPress plugins by Pluginus.Net. Attackers can trick authenticated administrators into unknowingly executing unwanted actions (modifying posts, products, or plugin settings) by leveraging the lack of anti-CSRF token validation on state-changing operations.

MitigationApply vendor patches when available; implement WordPress nonces on all state-changing AJAX and form actions; consider using a WAF with CSRF protection rules as an interim measure.

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
Bear Woocommerce Bulk Editor And Products Manager ProfessionalWordPress extension
Affected:< 1.1.4.2
Wolf Wordpress Posts Bulk Editor And Products Manager ProfessionalWordPress extension
Affected:< 1.0.8.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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Identify installed Pluginus plugins
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'Woocommerce Bulk Editor And Products Manager Professional' or 'Wordpress Posts Bulk Editor And Products Manager Professional' by Pluginus.Net.
    Affected if Either plugin is installed
  2. Check Bulk Editor version
    In Plugins list, locate the WooCommerce Bulk Editor plugin and note the version number displayed under the plugin name.
    Affected if Version is lower than 1.1.4.2
  3. Check Posts Editor version
    In Plugins list, locate the WordPress Posts Bulk Editor plugin and note the version number displayed under the plugin name.
    Affected if Version is lower than 1.0.8.2
  4. Verify plugin is active
    In Plugins > Installed Plugins, confirm the status column shows the plugin as 'Active'.
    Affected if Plugin is active and version is in the vulnerable range

User is affected if either Pluginus Bulk Editor plugin is installed, active, and running a version below 1.1.4.2 (WooCommerce) or below 1.0.8.2 (Posts), allowing authenticated administrators to access the vulnerable admin interface.

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.2 / 1.1.4.2 or later
Fixed in 1.0.8.21.1.4.2
Interim mitigation

Apply vendor patches when available; implement WordPress nonces on all state-changing AJAX and form actions; consider using a WAF with CSRF protection rules as an interim measure.

Recommended fix High confidence

WOLF: upgrade to version 1.0.8.2 | BEAR: upgrade to version 1.1.4.2

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
  3. 3. Locate 'WOLF – WordPress Posts Bulk Editor and Manager Professional' and check if update to version 1.0.8.2 is available.
  4. 4. Locate 'BEAR – Bulk Editor and Products Manager Professional for WooCommerce' and check if update to version 1.1.4.2 is available.
  5. 5. Update each plugin to its respective fixed version (WOLF to 1.0.8.2, BEAR to 1.1.4.2).
  6. 6. Verify the updates were successful by checking the plugin version numbers.
  7. 7. Test the core functionality of each plugin to ensure the update did not break existing features.

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

Fix this in Bear Woocommerce Bulk Editor And Products Manager Professional Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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