# CVE-2026-33386: XSS in QuickCMS


- **Severity:** Low 2.3 (`CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 May 2026
- **Updated:** 29 May 2026
- **Also known as:** GHSA-wq6v-xp72-v7h5

## What is CVE-2026-33386?

CVE-2026-33386 is a low-severity vulnerability in OpenSolution QuickCMS, published on 29 May 2026. 

### Official description

QuickCMS is vulnerable to Cross-Site Scripting (XSS) through its insecure HTTP-based plugin‑fetching mechanism. A malicious attacker can perform a Man‑in‑the‑Middle (MITM) attack by impersonating the opensolution.org server and serving arbitrary HTML or JavaScript at the plugin list endpoint. When a user accesses the plugin page, the malicious content is automatically fetched, rendered, and executed.

This issue was fixed in a patch to version 6.8 published on 15.05.2026, deployments without this patch are still vulnerable.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-33386 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-33386 is a low-severity vulnerability in OpenSolution QuickCMS, published on 29 May 2026. 
Exploitation: There is no known exploitation of CVE-2026-33386 in the wild and no public exploit code.

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

## Sources

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

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