LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1673: BEAR – Bulk Editor and Products Manager Professional for WooCommerce by Pluginus.Net <= 1.1.5 - Cross-Site Request Forgery to Taxonomy Term Deletion

The 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_delete_tax_term() function. This makes it possible for unauthenticated attackers to delete WooCommerce taxonomy terms (categories, tags, etc.) via a forged request granted they can trick a site administrator or shop manager into performing an action such as clicking on a link.

MediumCVSS 4.3Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

A malicious site or link can misuse an authenticated administrator’s or shop manager’s session to delete WooCommerce categories, tags, or other taxonomy terms. The attacker needs the privileged user to take an action, such as clicking a link. Successful abuse could disrupt catalog organization and product discovery, but the supplied sources report no confidentiality impact.

Executive priority

Treat this as a prompt remediation item for affected commerce sites, especially stores relying heavily on categories and tags. It is not supported as an emergency, actively exploited issue, but successful abuse could require catalog restoration and interrupt product navigation. Prioritize inventory, backups, and confirmation of vendor remediation.

Technical view

BEAR versions through 1.1.5 lack nonce validation in woobe_delete_tax_term(), enabling cross-site request forgery. The CVSS 3.1 score is 4.3: network-accessible, low complexity, no attacker privileges, required user interaction, and low integrity impact. The supplied evidence does not establish a fixed version.

Likely exposure

Exposure is limited to WordPress stores running BEAR through version 1.1.5 where an authenticated administrator or shop manager can be induced to submit a forged request. Sites without the plugin, with a confirmed remediated version, or without an exposed privileged session are not described as vulnerable by the supplied evidence.

Exploitation context

The attacker does not need authentication but must trick an authenticated administrator or shop manager into acting. The source bundle marks this CVE as absent from KEV and provides no evidence of active exploitation. Exploitation status should therefore be treated as unconfirmed.

Researcher notes

CWE-352 applies because the deletion function lacks nonce validation. The attack targets integrity rather than confidentiality and requires a privileged victim’s interaction. The bundle includes WordPress Trac changesets, but it does not explain whether either fully fixes the issue or name a safe version. Affected-version metadata also contains an inconsistent versions value of "0" despite the description stating through 1.1.5.

Mitigation direction

  • Inventory WordPress stores and identify BEAR installations running version 1.1.5 or earlier.
  • Check Pluginus and WordPress plugin guidance for a confirmed remediated release or official mitigation.
  • Update to a vendor-confirmed remediated version after backup and compatibility testing.
  • If remediation is unavailable, assess temporarily disabling the plugin based on store requirements.
  • Remind privileged users to avoid untrusted links while authenticated to WordPress administration.

Validation and detection

  • Confirm the installed BEAR version from trusted WordPress inventory or plugin records.
  • Verify vendor guidance identifies the installed release as remediated before closing the finding.
  • Review taxonomy terms for unexpected category, tag, or related term deletions.
  • Review available WordPress, web-server, and security logs for suspicious taxonomy-deletion requests.
  • Confirm privileged accounts use appropriate roles and are not shared unnecessarily.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-1673 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
5Timeline events
1ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Wordfence

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2026-1673Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. Source timelineWordfence

    Vendor Notified

  3. Source timelineWordfence

    Disclosed

  4. CVE publishedCVE Program

    The CVE record was published.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
realmag777BEAR – Bulk Editor and Products Manager Professional for WooCommerce by Pluginus.Net0unaffected
Weakness

CWE details

CWE-352

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs