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

CVE-2026-44669

HIGH · 8.7 CVSS v3.1 Published 2026-05-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
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
FACTION is a PenTesting Report Generation and Collaboration Framework. Prior to 1.8.3, Faction is vulnerable to stored cross-site scripting (XSS) via attachment filenames in assessment file preview flows. User-supplied filename values are persisted and later rendered into HTML/attribute contexts without output encoding, allowing attacker-controlled JavaScript to execute in the browser of any user who views the affected page. Because the payload is stored server-side and rendered to other users, exploitation is persistent and can impact privileged accounts. This vulnerability is fixed in 1.8.3.

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

FACTION versions prior to 1.8.3 contain a stored XSS vulnerability in the assessment file preview functionality. Attackers can embed malicious JavaScript in attachment filenames that are persisted to the database and later rendered without output encoding into HTML/attribute contexts when users view the affected preview pages.

MitigationUpgrade to FACTION version 1.8.3 or later. If immediate upgrade is not feasible, implement output encoding for all filename values before rendering them in HTML contexts.

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
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/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. Identify FACTION version
    Locate the installed FACTION version by checking the application metadata, about page, or version file (commonly found in installation directory, configuration files, or the web interface footer). Compare it to the affected range: versions prior to 1.8.3 are vulnerable.
    Affected if Installed version is less than 1.8.3
  2. Confirm assessment file preview is accessible
    Verify whether the assessment module and its file preview functionality are enabled in the application. Check user role permissions or administrative settings that control access to assessment-related features.
    Affected if Assessment file preview functionality is enabled and accessible to users
  3. Identify database with assessment attachments
    Locate the database storing FACTION application data. Identify tables related to assessments and file attachments (look for tables containing fields like filename, attachment_name, or file_path associated with assessment records).
    Affected if Database contains assessment attachment records with filename fields
  4. Inspect attachment filenames for injection payloads
    Query the attachment table for suspicious patterns in filenames, such as HTML tags (<script>, <img onerror=, javascript:, or other tag attributes containing event handlers). Examine raw filename values rather than rendered output.
    Affected if Any attachment filenames contain unsanitized HTML or JavaScript syntax
  5. Review application output encoding
    Examine how attachment filenames are displayed in the file preview interface. Test by accessing the assessment file preview with a benign test filename containing special characters (e.g., <test>) and verify if characters are rendered as plaintext or interpreted as HTML.
    Affected if Special characters in filenames are rendered as active HTML rather than HTML-encoded

A user is affected if running FACTION version prior to 1.8.3 with assessment file preview enabled, and the database contains attachment filenames that include unencoded HTML/JavaScript content.

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

Upgrade to FACTION version 1.8.3 or later. If immediate upgrade is not feasible, implement output encoding for all filename values before rendering them in HTML contexts.

Recommended fix High confidence

1.8.3

  1. 1. Identify the current FACTION installation version by checking the application or documentation.
  2. 2. Create a full backup of the FACTION database and configuration files before proceeding with the upgrade.
  3. 3. Follow the official FACTION upgrade documentation to upgrade to version 1.8.3.
  4. 4. After upgrading, verify that the application is running correctly and the version is confirmed as 1.8.3.

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-44669 — 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-44669 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