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

CVE-2026-61501

MEDIUM · 6.1 CVSS v3.1 Published 2026-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges 5 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
Rejetto HFS 3.0.0 through 3.2.0 renders log entries in the administration panel as HTML without sanitization. A remote unauthenticated attacker can submit a failed login with a crafted username that is written to the error log and executes JavaScript in an administrator's browser when the logs are viewed, allowing the attacker to create accounts or execute code on the server with the administrator's privileges.

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

Rejetto HFS versions 3.0.0-3.2.0 contains a stored XSS vulnerability in the admin panel log viewer. An unauthenticated attacker can inject malicious JavaScript via a crafted username in a failed login attempt. When administrators view the error logs in the web interface, this payload executes, allowing the attacker to perform actions with the administrator's session.

MitigationSanitize all log output with proper HTML encoding before rendering in the admin panel, and implement input validation on the username field to reject or escape special characters. Upgrade to a patched version once 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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify if Rejetto HFS is running
    Check running processes or services for HFS executable, or access the web interface on the default HTTP port (port 80 or configured port)
    Affected if HFS is running and accessible on the network
  2. Determine the installed HFS version
    Access the HFS web interface and look for version information, typically in the admin panel or footer of the page
    Affected if The version falls within 3.0.0 to 3.2.0 inclusive
  3. Check admin panel access
    Attempt to access the admin panel path (usually /?admin or /~admin) on the HFS server
    Affected if Admin panel is accessible and authentication can be attempted
  4. Inspect error logs for suspicious entries
    In the admin panel, navigate to the log viewer or error logs section and examine failed login entries for unexpected username patterns containing script tags or HTML
    Affected if Log entries contain unsanitized username input with <script> tags or HTML markup that renders as executable code

A user is affected if they are running HFS version 3.0.0-3.2.0 with the admin panel accessible and the error logs contain unencoded username values from failed login attempts.

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

Sanitize all log output with proper HTML encoding before rendering in the admin panel, and implement input validation on the username field to reject or escape special characters. Upgrade to a patched version once available.

Recommended fix High confidence

HFS version 3.2.1 or later

  1. 1. Identify the currently installed Rejetto HFS version by checking the application or its configuration
  2. 2. If running version 3.0.0 through 3.2.0, plan for an upgrade to version 3.2.1 or later
  3. 3. Before upgrading, backup the current HFS configuration and any important data
  4. 4. Download the latest stable version of Rejetto HFS from the official GitHub repository (github.com/rejetto/hfs)
  5. 5. Stop the HFS service or ensure no active file transfers are in progress
  6. 6. Install the new version (3.2.1 or later) following the official upgrade instructions
  7. 7. Start the HFS service and verify the application is running correctly
  8. 8. Test the log viewing functionality in the admin panel to confirm the fix is applied
Caveat Review release notes for any configuration or feature changes between 3.0.0-3.2.0 and 3.2.1+; minor version upgrades typically have minimal breaking changes

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