# CVE-2026-120274: beecue FastBee Groovy Script Executor script code injection


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 1 Nov 2026
- **Updated:** 2 Nov 2026
- **Also known as:** GHSA-fcpv-5322-c269

## What is CVE-2026-120274?

CVE-2026-120274 is a medium-severity vulnerability in beecue FastBee, published on 1 Nov 2026. 

### Official description

A vulnerability was identified in beecue FastBee up to 2.1.0. Affected by this issue is some unknown functionality of the file /iot/script of the component Groovy Script Executor. The manipulation leads to code injection. The attack is possible to be carried out remotely. The identifier of the patch is 890a33846005a937a58cccd738b7fb9821b82ea9. It is suggested to install a patch to address this issue.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2026-120274?


## How do I fix CVE-2026-120274?

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

## Is CVE-2026-120274 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120274 and fix it if it is affected.

What it is: CVE-2026-120274 is a medium-severity vulnerability in beecue FastBee, published on 1 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120274 in the wild and no public exploit code.

Affected product: beecue FastBee. 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-2026-120274/ (Markdown: https://insights.sbomify.com/CVE-2026-120274/index.md)
```

## Sources

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

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