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

CVE-2026-55746

HIGH · 7.6 CVSS v3.1 Published 2026-06-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
Cotonti 1.0.0 (master branch, commit f43f1fc3) is vulnerable to stored Cross-Site Scripting in the Personal File Storage (PFS) module. A folder title (pff_title) is imported with the 'TXT' filter, which does not strip or encode HTML (the tag check in cot_import is disabled), so an authenticated user can store HTML/JavaScript in a folder title.

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

Cotonti 1.0.0 PFS module stores folder titles (pff_title) without sanitization because the 'TXT' import filter does not strip or encode HTML. The title is assigned to PFF_ROW_TITLE in pfs.main.php without htmlspecialchars() and output unescaped in pfs.tpl, allowing authenticated users to inject malicious scripts that execute when other users view folder listings.

MitigationApply htmlspecialchars() encoding to the folder title before assigning it to PFF_ROW_TITLE in pfs.main.php, or ensure the template uses escaped output syntax for {PFF_ROW_TITLE}. Additionally, enable or implement proper HTML tag filtering in the cot_import 'TXT' filter.

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
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/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. Confirm Cotonti installation and version
    Locate the Cotonti installation directory and check for version.php or version information in index.php, system/functions.php, or a version constant file. Typical paths include /index.php or /system/functions.php. Search for 'Cotonti' or '1.0.0' in these files.
    Affected if The installed version is Cotonti 1.0.0 (exact match)
  2. Verify PFS module is installed and enabled
    Check for the presence of the PFS module files in the modules directory, typically at /modules/pfs/ or /modules/pfs/pfs.main.php and /modules/pfs/pfs.tpl. Also check the Cotonti database or configuration for module status.
    Affected if The PFS module files exist and the module is enabled in the Cotonti configuration
  3. Inspect pfs.main.php for unescaped title assignment
    Open /modules/pfs/pfs.main.php and search for the assignment of PFF_ROW_TITLE. Look for a line that assigns the folder title (pff_title) directly to PFF_ROW_TITLE without applying htmlspecialchars() or equivalent encoding. For example: $t->assign('PFF_ROW_TITLE', $row['pff_title']);
    Affected if PFF_ROW_TITLE is assigned without htmlspecialchars() encoding around the folder title variable
  4. Inspect pfs.tpl for unescaped template output
    Open the template file pfs.tpl (typically in /modules/pfs/tpl/pfs.tpl or the theme's templates directory) and search for {PFF_ROW_TITLE}. Verify if it uses escaped syntax like {{PFF_ROW_TITLE}} or unescaped syntax like {PFF_ROW_TITLE}.
    Affected if The template uses {PFF_ROW_TITLE} (unescaped) rather than an escaped variant
  5. Check TXT import filter for HTML filtering
    Examine the cot_import function or TXT filter implementation in Cotonti's core (typically in system/functions.php or system/core.php). Look for how the 'TXT' filter handles input and whether it includes HTML stripping or encoding logic.
    Affected if The TXT filter does not perform HTML entity encoding or tag stripping on input values

A user is affected if they run Cotonti version 1.0.0 with the PFS module enabled, and the source code shows PFF_ROW_TITLE assigned without htmlspecialchars() or the template outputs {PFF_ROW_TITLE} unescaped.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply htmlspecialchars() encoding to the folder title before assigning it to PFF_ROW_TITLE in pfs.main.php, or ensure the template uses escaped output syntax for {PFF_ROW_TITLE}. Additionally, enable or implement proper HTML tag filtering in the cot_import 'TXT' filter.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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