BEAR taxonomy update CSRF can modify arbitrary terms
BEAR before 1.2.2 updates taxonomy terms without verifying a CSRF nonce or checking the acting user's capabilities. An attacker can trick a logged-in privileged user into visiting a crafted page that modifies arbitrary terms. The authoritative export does not identify the handler, taxonomy, term identifier, or mutable fields.
- Component
- BEAR
- Plugin slug
bear- Affected
- < 1.2.2
- Safe version
1.2.2- Published
- Sep 12, 2026
This CVE was published Sep 12, 2026 and is one of 3 known issues for this plugin.
Update, patch or deactivate.
Update BEAR to 1.2.2 or later. The authoritative affected range ends before 1.2.2. The application-level fix must verify a nonce, require the appropriate term-management capability for the targeted taxonomy, and validate the exact term and fields being changed.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The BEAR WordPress plugin before 1.2.2 does not verify a CSRF nonce or check user capabilities before updating taxonomy terms, allowing an attacker to modify arbitrary terms by tricking a logged-in privileged user into visiting a crafted page.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N