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

CVE-2026-58144

MEDIUM · 5.4 CVSS v3.1 Published 2026-07-09
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 6 weeks old

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 Siena 0.9.26 and earlier contains a stored cross-site scripting vulnerability that allows authenticated users with PFS access to inject arbitrary script payloads by supplying malicious HTML in the ntitle parameter processed through the TXT filter in pfs.main.php. Attackers can create a folder with a crafted title containing script tags that are stored unescaped in the database and execute in the browser of any user who views the folder listing, including administrators.

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

Stored XSS vulnerability in Cotonti Siena PFS (Personal File Storage) allows authenticated users to inject arbitrary script payloads via the ntitle parameter. The TXT filter in pfs.main.php fails to properly sanitize HTML input, allowing malicious code to be stored in the database and executed in the browsers of any user viewing the folder listing.

MitigationImplement input validation and output encoding on the ntitle parameter in pfs.main.php to neutralize script injection vectors; update to patched version if available.

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. Confirm Cotonti Siena installation and version
    Locate the main version file (typically version.php or similar in the root directory) and read the version number. Compare against any available patched versions.
    Affected if The installed version is older than the patched version and falls within the vulnerable release range.
  2. Verify PFS module is enabled
    Check the system configuration files or admin panel to confirm the Personal File Storage (PFS) module is active. Look for pfs in the modules directory and configuration settings.
    Affected if PFS module is installed and enabled, making the vulnerable code path accessible.
  3. Locate and inspect pfs.main.php
    Find pfs.main.php in the modules/pfs/ directory. Examine the TXT filter handling code that processes the ntitle parameter. Look for lack of HTML sanitization or input validation on this parameter.
    Affected if The file contains TXT filter logic for ntitle without proper HTML entity encoding or input validation.
  4. Check for authenticated user access to PFS
    Verify that user authentication is configured and that registered users can access the PFS functionality. Check user permissions related to file uploads and folder management.
    Affected if Authenticated users exist and have permissions to create or modify PFS entries, allowing them to supply the ntitle parameter.
  5. Inspect database for stored content
    Query the database tables related to PFS (such as pfs or similar naming) to check for any existing entries with HTML script tags in title fields. Examine stored ntitle values for unsanitized content.
    Affected if Database contains HTML or script tags in PFS title fields, indicating successful exploitation.

A user is affected if running a vulnerable Cotonti Siena version with PFS module enabled and the pfs.main.php TXT filter lacks proper sanitization on the ntitle parameter, allowing stored XSS execution.

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

Implement input validation and output encoding on the ntitle parameter in pfs.main.php to neutralize script injection vectors; update to patched version if available.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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