dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-41467

MEDIUM · 5.4 CVSS v3.1 Published 2026-04-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
ProjeQtor versions 7.0 through 12.4.3 contain a stored cross-site scripting vulnerability in the file upload functionality where the checkValidFileName() function fails to restrict HTML and HTM file uploads. Authenticated attackers can upload HTML files containing arbitrary JavaScript through the image upload or attachment endpoints, and any user accessing the uploaded file URL will execute the embedded JavaScript in their browser.

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 confidence

ProjeQtor versions 7.0-12.4.3 have a stored XSS vulnerability in the file upload functionality where checkValidFileName() fails to block HTML/HTM file uploads. Authenticated attackers can upload malicious HTML files containing arbitrary JavaScript through image or attachment endpoints, which executes in victim browsers when they access the uploaded file URL.

MitigationRestrict or block HTML/HTM file uploads in checkValidFileName(), implement Content-Type and file content validation, or disable HTML file uploads entirely until proper sanitization is in place.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify ProjeQtor version
    Locate the version number in the ProjeQtor installation (typically visible in the application header, about page, or in a config/version file). Compare it against the affected range 7.0 through 12.4.3.
    Affected if Installed version falls within 7.0 to 12.4.3 inclusive.
  2. Confirm file upload is enabled
    Log in as an authenticated user and navigate to the image or attachment upload functionality (typically in project documentation, ticket attachments, or user profile sections).
    Affected if File upload features are accessible to authenticated users.
  3. Inspect checkValidFileName() function
    Locate the checkValidFileName() function in the ProjeQtor source code (search in include or tool folders). Examine whether it contains logic to reject .html or .htm file extensions.
    Affected if The function does not block or reject HTML/HTM file extensions.
  4. Test HTML file upload capability
    Attempt to upload a test file with .html or .htm extension through the attachment or image upload endpoint. Check if the upload succeeds and the file becomes accessible via a direct URL.
    Affected if HTML/HTM files can be uploaded and accessed via a URL that executes in a browser.

The environment is affected if ProjeQtor version is between 7.0 and 12.4.3 AND the checkValidFileName() function allows HTML/HTM file uploads without blocking them.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict or block HTML/HTM file uploads in checkValidFileName(), implement Content-Type and file content validation, or disable HTML file uploads entirely until proper sanitization is in place.

Recommended fix Moderate confidence

ProjeQtor version 12.5 or latest stable release

  1. 1. Navigate to the ProjeQtor administration panel or check the official ProjeQtor download page at www.projeqtor.com for the latest stable release
  2. 2. Download the most recent version of ProjeQtor (version 12.5 or later, as versions 7.0 through 12.4.3 are affected)
  3. 3. Create a complete backup of the current ProjeQtor installation, including the database
  4. 4. Test the upgrade in a staging environment to verify functionality
  5. 5. Apply the upgrade to the production environment following standard ProjeQtor upgrade procedures
  6. 6. Verify that the checkValidFileName() function now properly rejects HTML and HTM file uploads
  7. 7. Confirm that legitimate file upload functionality (images, attachments) continues to work correctly
Caveat Review ProjeQtor release notes between 12.4.3 and the target version for any breaking changes or database schema updates that may require migration steps

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41467 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41467 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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