# CVE-2025-44110: Cross-site scripting in n/a

> An attacker can inject malicious scripts into the forum description field, potentially leading to session hijacking or code execution.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 May 2025
- **Updated:** 16 May 2025
- **Also known as:** GHSA-g45r-4866-8vwq

## What is CVE-2025-44110?

CVE-2025-44110 is a medium-severity cross-site scripting vulnerability in n/a, published on 15 May 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

FluxBB 1.5.11 is vulnerable to Cross Site Scripting (XSS) in via the Forum Description Field in admin_forums.php.

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

## Which versions are affected by CVE-2025-44110?

It affects 1 product.


Products: Fluxbb Fluxbb.

## How do I fix CVE-2025-44110?

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

## Is CVE-2025-44110 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-3621](https://insights.sbomify.com/CVE-2011-3621/): Security feature bypass in FluxBB (critical 9.8)
- [CVE-2014-9574](https://insights.sbomify.com/CVE-2014-9574/): Path traversal in n/a (critical 9.3)
- [CVE-2020-28873](https://insights.sbomify.com/CVE-2020-28873/): Denial of service in n/a (high 7.5)
- [CVE-2014-10029](https://insights.sbomify.com/CVE-2014-10029/): SQL injection in n/a (high 7.5)
- [CVE-2021-43677](https://insights.sbomify.com/CVE-2021-43677/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-44110 and fix it if it is affected.

What it is: CVE-2025-44110 is a medium-severity cross-site scripting vulnerability in n/a, published on 15 May 2025. Any signed-in user can exploit it over the network, 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-2025-44110 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-2025-44110/ (Markdown: https://insights.sbomify.com/CVE-2025-44110/index.md)
```

## Sources

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

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