# CVE-2026-26682: An issue in fastCMS before v.0.1.6 allows a local attacker to execute arbitrary code via the PluginController.java component


- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Feb 2026
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-5859-4v8q-r354

## What is CVE-2026-26682?

CVE-2026-26682 is a high-severity vulnerability in n/a, published on 26 Feb 2026. 

### Official description

An issue in fastCMS before v.0.1.6 allows a local attacker to execute arbitrary code via the PluginController.java component

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Xjd2020 Fastcms.

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

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

## Is CVE-2026-26682 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-26682 exists.

## Other vulnerabilities in n/a

- [CVE-2022-4300](https://insights.sbomify.com/CVE-2022-4300/): FastCMS Template edit injection (medium 6.3)
- [CVE-2025-2593](https://insights.sbomify.com/CVE-2025-2593/): FastCMS list sql injection (medium 5.3)
- [CVE-2024-7733](https://insights.sbomify.com/CVE-2024-7733/): FastCMS New Article Category Page cross site scripting (medium 5.3)
- [CVE-2023-1111](https://insights.sbomify.com/CVE-2023-1111/): FastCMS New Article Tab cross site scripting (medium 5.1)
- [CVE-2025-1332](https://insights.sbomify.com/CVE-2025-1332/): FastCMS Template Menu menu cross site scripting (medium 4.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-26682 is a high-severity vulnerability in n/a, published on 26 Feb 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-26682 exists.

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

## Sources

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

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