CVE-2026-41466
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedProjeQtor 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceProjeQtor versions 7.0-12.4.3 contain a stored XSS vulnerability in the checkValidHtmlText() function within Security.php. The function detects only specific attack patterns but returns unsanitized strings without proper output encoding, allowing attackers to bypass the filter using alternative syntax like img tags with event handlers. Malicious payloads are stored in the database and execute when users view affected content.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify ProjeQtor installation and versionLocate the ProjeQtor installation directory. Check version.php or similar version file to confirm the installed version falls within 7.0 through 12.4.3Affected if The installed version is between 7.0 and 12.4.3 inclusive
-
Locate the vulnerable Security.php fileNavigate to the include directory or similar path within the ProjeQtor installation and locate Security.php. Confirm the checkValidHtmlText() function exists within this fileAffected if The file Security.php contains the checkValidHtmlText() function
-
Inspect the checkValidHtmlText() function implementationOpen Security.php and examine the checkValidHtmlText() function. Look for the code that returns strings without proper output encoding - specifically check if the function returns the original input string after partial pattern matchingAffected if The function returns unsanitized strings and relies solely on pattern detection without encoding output
-
Determine if user-generated content features are in useIdentify which database tables and application modules accept HTML input and route it through checkValidHtmlText(). Common areas include notes, descriptions, comments, or rich text fieldsAffected if User-generated content is stored and displayed using fields processed by checkValidHtmlText()
Your environment is affected if you run ProjeQtor version 7.0-12.4.3, the checkValidHtmlText() function in Security.php returns unsanitized strings, and your instance accepts user input that passes through this function to be displayed in the browser.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataFix the checkValidHtmlText() function to either implement proper output encoding for all returned strings or use a robust sanitization library that handles edge cases. Identify and test all input paths that use this function.
- Consultation6.0 h
- Implementation10.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,104.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41466 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-41466 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data