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

CVE-2026-29971

MEDIUM · 6.1 CVSS v3.1 Published 2026-04-27
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

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
A reflected cross-site scripting (XSS) vulnerability exists in WebFileSys version before 2.32.0 and fixed in v.2.32.0. User-controlled input is reflected into HTML and JavaScript contexts without proper output encoding, allowing arbitrary JavaScript execution in the victim's browser via the ftpBackup functionality, authentication input handling, search functionality, and error message rendering components

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

Reflected cross-site scripting (XSS) vulnerability in WebFileSys versions prior to 2.32.0 allows arbitrary JavaScript execution via improper handling of user-controlled input. Multiple components are affected: ftpBackup functionality, authentication input fields, search functionality, and error message rendering—all fail to properly encode output before reflecting it into HTML/JavaScript contexts.

MitigationUpgrade WebFileSys to version 2.32.0 or later, which implements proper output encoding for all user inputs across the affected components.

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 installed WebFileSys version
    Locate the version information in the application (typically in an about page, footer, or version file) and note the exact version number
    Affected if Version is below 2.32.0 (e.g., 2.31.x, 2.30.x, or earlier)
  2. Determine if ftpBackup functionality is accessible
    Check if the ftpBackup feature is enabled or accessible in the application configuration or navigation
    Affected if ftpBackup is enabled and the WebFileSys version is prior to 2.32.0
  3. Assess authentication form exposure
    Identify login or authentication entry points in the WebFileSys interface and determine if they accept user input
    Affected if Authentication input fields are present and the WebFileSys version is prior to 2.32.0
  4. Verify search functionality presence
    Locate any search or query input fields provided by the WebFileSys application
    Affected if Search functionality exists and the WebFileSys version is prior to 2.32.0
  5. Check error message handling
    Trigger error conditions (such as invalid input or failed operations) and observe how error messages are rendered
    Affected if Error messages are displayed to users and the WebFileSys version is prior to 2.32.0

A user is affected if their WebFileSys installation is version 2.32.0 or lower AND any of the affected components (ftpBackup, authentication, search, error rendering) are enabled or accessible.

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 WebFileSys to version 2.32.0 or later, which implements proper output encoding for all user inputs across the affected components.

Recommended fix High confidence

version 2.32.0

  1. Identify the current version of WebFileSys being used
  2. Download WebFileSys version 2.32.0 or later from the official source (github.com or www.webfilesys.de)
  3. Back up the current installation and configuration files
  4. Replace the existing WebFileSys files with the updated v2.32.0 files
  5. Restore the configuration from the backup
  6. Verify the upgrade was successful by checking the version number
  7. Test the application functionality, particularly the ftpBackup feature, authentication, search, and error message handling

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,960
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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