CVE-2026-1672
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 · uneditedThe BEAR – Bulk Editor and Products Manager Professional for WooCommerce by Pluginus.Net plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.1.5. This is due to missing nonce validation on the woobe_redraw_table_row() function. This makes it possible for unauthenticated attackers to update WooCommerce product data including prices, descriptions, and other product fields via a forged request granted they can trick a site administrator or shop manager into performing an action such as clicking on a link.
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 confidenceThe BEAR Bulk Editor plugin for WooCommerce has a CSRF vulnerability in the woobe_redraw_table_row() function due to missing nonce validation. This allows unauthenticated attackers to forge requests that modify WooCommerce product data including prices and descriptions, provided they can trick an administrator into clicking a malicious link.
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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Locate BEAR Bulk Editor plugin installationIn WordPress admin, go to Plugins > Installed Plugins and look for 'BEAR - Bulk Editor' or check the plugin files in /wp-content/plugins/bear-bulk-editor/ for the main PHP file to read the version headerAffected if Plugin is not found - not applicable
-
Determine installed plugin versionRead the version number from the plugin header in the main plugin PHP file (usually bear-bulk-editor.php) or from the WordPress plugins admin pageAffected if Version is present and less than 1.1.6 (e.g., 1.1.5, 1.1.0, etc.) - vulnerable to CSRF
-
Verify the vulnerable function existsExamine the plugin source code for the woobe_redraw_table_row() function in ajax handlers - check if it contains nonce verification using wp_verify_nonce or check_admin_refererAffected if Function exists and processes product data modifications without nonce validation - vulnerable
-
Confirm admin authentication requirement for exploitationThe CSRF attack requires a logged-in administrator or shop manager to click a malicious URL - the plugin must have an active admin session accessAffected if Site has active administrator or shop manager accounts who could be targeted - exploitation possible if version is vulnerable
If BEAR Bulk Editor plugin is installed with a version before 1.1.6 and the woobe_redraw_table_row() function lacks nonce validation, the site is vulnerable to CSRF attacks that can modify product data.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement nonce validation on the woobe_redraw_table_row() function and all state-changing operations. Consider using WordPress nonces and checking user capabilities. As a temporary workaround, advise administrators not to click untrusted links.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1672 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-1672 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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