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

CVE-2024-30200

MEDIUM · 6.1 CVSS v3.1 Published 2024-03-28
Fix available
A fix is available. Upgrade to 1.1.4.3 or later.
See remediation →
68/100
Remediation priority · Elevated
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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in realmag777 BEAR allows Reflected XSS.This issue affects BEAR: from n/a through 1.1.4.2.

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

Reflected XSS vulnerability in realmag777 BEAR plugin/theme allows attackers to inject malicious scripts via unsanitized user input that gets reflected in web pages. The CVSS 6.1 indicates the vulnerability is remotely exploitable and requires user interaction (e.g., clicking a crafted link).

MitigationImplement proper output encoding/escaping and input validation on all user-supplied data before reflecting it in HTML responses. Apply context-appropriate encoding (HTML, URL, JavaScript) based on where the data is inserted.

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

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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. Locate the BEAR plugin installation directory
    Navigate to your WordPress installation /wp-content/plugins/ directory and search for a folder containing 'bear' or 'bulk-editor' in the name. The plugin is typically named 'woobe-bulk-editor' or similar.
    Affected if The plugin directory exists on the server
  2. Identify the installed plugin version
    Open the main plugin PHP file (usually named 'bear.php', 'woobe.php', or similar in the plugin folder) and look for a version comment/constant at the top of the file. Alternatively, check the plugin's readme.txt file in the 'Tags' section or the 'Version' header in the main plugin file.
    Affected if The version number found is lower than 1.1.4.3
  3. Verify the plugin is active
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'BEAR - WooCommerce Bulk Editor And Products Manager Professional' in the list and confirm it shows as 'Active'.
    Affected if The plugin is activated on the WordPress site
  4. Check for vulnerable input reflection points
    Access the plugin's frontend or admin interface where user input is accepted (such as search fields, filter parameters, or form inputs). Inspect the page source or use browser developer tools to see if URL parameters or form inputs are reflected directly in the HTML output without visible sanitization.
    Affected if User-supplied parameters are reflected in the page without proper HTML encoding

You are affected if the BEAR plugin is installed, active, and the installed version is lower than 1.1.4.3, as this version range contains the reflected XSS vulnerability in unsanitized user input handling.

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.1.4.3 or later
Fixed in 1.1.4.3
Interim mitigation

Implement proper output encoding/escaping and input validation on all user-supplied data before reflecting it in HTML responses. Apply context-appropriate encoding (HTML, URL, JavaScript) based on where the data is inserted.

Recommended fix Moderate confidence

1.1.4.3

  1. Backup your WordPress site and database before performing any updates
  2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. Locate the 'BEAR - WooCommerce Bulk Editor And Products Manager Professional' plugin by realmag777
  4. Verify the currently installed version is below 1.1.4.3
  5. Update the plugin to version 1.1.4.3 or later through the WordPress plugins interface
  6. Verify the update was successful by confirming the installed version now shows 1.1.4.3 or higher
  7. Test the plugin functionality to ensure the update did not break expected 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
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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