# CVE-2026-41466: ProjeQtor < 12.4.4 Stored XSS via checkValidHtmlText()

> Attackers can inject malicious scripts via stored XSS in ProjeQtor, potentially leading to code execution or account takeover in victim browsers.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA: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:** 27 Apr 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-8pgv-76j9-qj4g

## What is CVE-2026-41466?

CVE-2026-41466 is a medium-severity cross-site scripting vulnerability in ProjeQtor, published on 27 Apr 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

ProjeQtor versions 7.0 through 12.4.3 contain a stored cross-site scripting vulnerability in the checkValidHtmlText() function within Security.php that fails to properly sanitize user input by only detecting specific patterns while returning unsanitized strings without output encoding. Attackers can inject malicious payloads that bypass the filter using alternative syntax such as img tags with event handlers, which are stored and executed in the browsers of users viewing the affected content.

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

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


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

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

## Is CVE-2026-41466 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-41466 is a medium-severity cross-site scripting vulnerability in ProjeQtor, published on 27 Apr 2026. 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-2026-41466 exists.

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

## Sources

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

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