# CVE-2017-20026: HumHub Reflected cross site scriting

> Remote attackers can execute arbitrary scripts in victims' browsers via reflected XSS in HumHub, potentially leading to session hijacking or data theft.

- **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:** 9 Jun 2022
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-m7qr-8cph-5cpw

## What is CVE-2017-20026?

CVE-2017-20026 is a medium-severity cross-site scripting vulnerability in unspecified HumHub, published on 9 Jun 2022. 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

A vulnerability has been found in HumHub up to 1.0.1 and classified as problematic. Affected by this vulnerability is an unknown functionality. The manipulation leads to cross site scripting (Reflected). The attack can be launched remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 1.1.1 is able to address this issue. It is recommended to upgrade the affected component.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-80 (Improper Neutralization of Script-Related HTML Tags in a Web Page)

## Which versions are affected by CVE-2017-20026?

It affects 1 product.


Products: Humhub Humhub.

## How do I fix CVE-2017-20026?

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

## Is CVE-2017-20026 being exploited?

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

## Other vulnerabilities in unspecified HumHub

- [CVE-2014-9528](https://insights.sbomify.com/CVE-2014-9528/): SQL injection in n/a (high 7.5)
- [CVE-2025-64442](https://insights.sbomify.com/CVE-2025-64442/): HumHub is vulnerable to XSS through its Meta Search component (high 7.1)
- [CVE-2026-29048](https://insights.sbomify.com/CVE-2026-29048/): HumHub: XSS in Button component (medium 6.9)
- [CVE-2024-52043](https://insights.sbomify.com/CVE-2024-52043/): User enumeration in HubHub (medium 6.9)
- [CVE-2022-24865](https://insights.sbomify.com/CVE-2022-24865/): Improper access control in humhub (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-20026 and fix it if it is affected.

What it is: CVE-2017-20026 is a medium-severity cross-site scripting vulnerability in unspecified HumHub, published on 9 Jun 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-20026 exists.

Affected product: unspecified HumHub. 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-2017-20026/ (Markdown: https://insights.sbomify.com/CVE-2017-20026/index.md)
```

## Sources

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

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