CVE-2026-61504
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 · uneditedRejetto HFS 3.0.0 through 3.2.0 does not escape file names in its fallback "basic" web listing, and this listing can be forced by any browser via the ?get=basic parameter. A user with upload permission - or an anonymous user on servers with an open upload folder - can store a file whose name contains script that executes in the browser of anyone viewing the listing.
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 · moderate confidenceRejetto HFS 3.0.0-3.2.0 contains a stored XSS vulnerability in its 'basic' web listing (accessible via ?get=basic parameter). File names are not escaped, allowing attackers with upload permissions to embed malicious JavaScript in filenames that executes in victims' browsers when viewing the directory listing.
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 checksWork through these to decide whether this CVE applies to you.
-
Check HFS versionLook in the application's main window, About section, or check the executable file properties to identify the installed version of Rejetto HFS.Affected if The installed version is 3.0.0 through 3.2.0 inclusive.
-
Verify basic listing is accessibleAttempt to access the web interface with the ?get=basic parameter appended to the server URL (e.g., http://yourserver:port/?get=basic) to confirm the basic listing template is available.Affected if The basic listing page loads without being disabled or returning an error.
-
Check for upload permissionsReview user accounts and their permission settings in the HFS administration panel to identify which users or groups have upload capabilities.Affected if Any user account has upload permissions enabled, allowing that user to place malicious filenames on the server.
-
Inspect basic template for escapingAccess the template configuration file for the basic listing (typically found in the templates or config section of the HFS web interface) and search for the code that renders filenames.Affected if The template directly outputs filename variables without HTML entity encoding or escaping functions applied.
You are affected if your HFS version is between 3.0.0 and 3.2.0, the basic listing is accessible, and any user has upload permissions while the template lacks filename escaping.
Generated from the published advisory. Verify against your own configuration.
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 · scopedSanitize/escape HTML entities in filenames when rendering the basic listing template, or implement filename validation on upload to reject names containing scriptable characters/tags.
HFS version > 3.2.0 (check GitHub releases for the latest stable version)
- Identify the currently installed HFS version by checking the application or its web interface
- Navigate to the official Rejetto HFS GitHub repository releases page
- Locate and download the latest stable release (version higher than 3.2.0)
- Before upgrading, backup your current HFS configuration and any custom settings
- Stop the HFS service
- Install the new version following the standard upgrade procedure
- Restart the HFS service
- Verify the installation by accessing the web interface
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2026-61504 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-61504 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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