# CVE-2023-4920: BEAR <= 1.1.3.3 - Cross-Site Request Forgery to Stored Cross-Site Scripting

> Attackers can trick admins into modifying settings and injecting scripts via CSRF, leading to stored XSS and potential site compromise.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 Oct 2023
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-w7q5-62h8-hhmc

## What is CVE-2023-4920?

CVE-2023-4920 is a medium-severity vulnerability in realmag777 BEAR – Bulk Editor and Products Manager Professional for WooCommerce by Pluginus.Net, published on 20 Oct 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The BEAR for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.1.3.3. This is due to missing or incorrect nonce validation on the woobe_save_options function. This makes it possible for unauthenticated attackers to modify the plugin's settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. Additionally, input sanitization and escaping is insufficient resulting in the possibility of malicious script injection.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2023-4920?

It affects 1 product.


Products: Pluginus Bear - Woocommerce Bulk Editor and Products Manager Professional.

## How do I fix CVE-2023-4920?

No fix has been published for CVE-2023-4920 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-4920 being exploited?

There is no known exploitation of CVE-2023-4920 in the wild and no public exploit code.

## Other vulnerabilities in realmag777 BEAR – Bulk Editor and Products Manager Professional for WooCommerce by Pluginus.Net

- [CVE-2024-30200](https://insights.sbomify.com/CVE-2024-30200/): WordPress BEAR plugin <= 1.1.4.2 - Reflected Cross Site Scripting (XSS) vulnerability (high 7.1)
- [CVE-2025-26775](https://insights.sbomify.com/CVE-2025-26775/): WordPress BEAR Plugin <= 1.1.4.4 - Cross Site Scripting (XSS) vulnerability (medium 5.9)
- [CVE-2024-24834](https://insights.sbomify.com/CVE-2024-24834/): WordPress BEAR Plugin <= 1.1.4 is vulnerable to Cross Site Scripting (XSS) (medium 5.9)
- [CVE-2023-4923](https://insights.sbomify.com/CVE-2023-4923/): BEAR <= 1.1.3.3 - Cross-Site Request Forgery to Product Deletion (medium 5.4)
- [CVE-2023-4924](https://insights.sbomify.com/CVE-2023-4924/): BEAR <= 1.1.3.3 - Missing Authorization to Product Deletion (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-4920 and fix it if it is affected.

What it is: CVE-2023-4920 is a medium-severity vulnerability in realmag777 BEAR – Bulk Editor and Products Manager Professional for WooCommerce by Pluginus.Net, published on 20 Oct 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-4920 in the wild and no public exploit code.

Affected product: realmag777 BEAR – Bulk Editor and Products Manager Professional for WooCommerce by Pluginus.Net. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-4920/ (Markdown: https://insights.sbomify.com/CVE-2023-4920/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-4920
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-4920
- OSV: https://osv.dev/vulnerability/CVE-2023-4920

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-4920/
Summaries are generated and may contain mistakes; the official description above is the record.