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

CVE-2026-44667

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 remediation verification file preview flows. User-supplied filename values are persisted and then rendered into HTML and attribute contexts without output encoding, allowing attacker-controlled JavaScript to execute in the browser of any user who opens the affected verification/remediation views. 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 cross-site scripting vulnerability in the remediation verification file preview functionality. Attackers can embed malicious JavaScript in attachment filenames that persist on the server and execute when other users view affected verification/remediation pages, because user-supplied filenames are rendered into HTML and attribute contexts without proper output encoding.

MitigationUpgrade to FACTION version 1.8.3 or later. As an interim measure, implement output encoding for all filename values before rendering in HTML/attribute contexts, and consider restricting file upload capabilities to trusted users only.

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 installation and version
    Locate the FACTION application installation directory and check the version file, or query the application's built-in version information endpoint if available
    Affected if The installed version is before 1.8.3 (e.g., 1.8.0, 1.7.x, 1.6.x)
  2. Determine if remediation verification feature is in use
    Check if users have access to or have created remediation verification flows, which typically involve file attachments for proof of remediation
    Affected if The remediation verification feature is enabled and users have created verification flows with attachments
  3. Inspect attachment storage for suspicious filenames
    Access the backend storage (database or file system) where attachment metadata is persisted, and examine the filename fields in the remediation verification attachment records
    Affected if Any attachment filenames contain HTML tags, JavaScript event handlers, or script-like patterns (e.g., <script, onerror=, javascript:)
  4. Review application logs for XSS attempt patterns
    Search application and web server logs for requests containing suspicious patterns in filename parameters related to verification flow attachments
    Affected if Logs show attempts to upload files with XSS payloads in filename fields

A user is affected if FACTION version is below 1.8.3 AND the remediation verification file preview feature is in use, with attachment filenames containing unencoded script content present in the system

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. As an interim measure, implement output encoding for all filename values before rendering in HTML/attribute contexts, and consider restricting file upload capabilities to trusted users only.

Recommended fix High confidence

1.8.3

  1. 1. Identify the current version of the FACTION installation by checking the application or its configuration files
  2. 2. Create a complete backup of the FACTION installation including all databases and configuration files
  3. 3. Upgrade the FACTION installation to version 1.8.3 or later
  4. 4. After upgrading, verify that the application functions correctly and the upgrade was successful
  5. 5. Confirm that attachment filenames in remediation verification file preview flows are now properly encoded before rendering

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44667 — 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-44667 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