dbcve.org
Aspera FaspexApplication · Ibm

CVE-2025-36226

MEDIUM · 5.4 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 5.0.15 or later.
See remediation →
58/100
Remediation priority · Elevated
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
IBM Aspera Faspex 5 5.0.0 through 5.0.14.3 is vulnerable to cross-site scripting. This vulnerability allows an authenticated user to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session.

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

IBM Aspera Faspex 5 versions 5.0.0 through 5.0.14.3 contains a stored cross-site scripting (XSS) vulnerability in its Web UI. An authenticated attacker can embed arbitrary JavaScript code into the interface, which executes in the browsers of other users viewing the affected content, potentially enabling credential theft through a trusted session.

MitigationUpgrade to IBM Aspera Faspex 5.0.14.4 or later. If no patch is available, implement output encoding and input validation on all user-supplied fields, and consider Content Security Policy headers to mitigate XSS execution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Aspera FaspexApplication
Affected:>= 5.0.0, < 5.0.15

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. Identify installed IBM Aspera Faspex version
    Log into the Aspera Faspex admin console or run the CLI command 'faspex --version' or check the package/version information in the installation directory
    Affected if The version number is 5.0.0 through 5.0.14.3 (or any version < 5.0.15)
  2. Confirm Web UI is enabled
    Access the Faspex web interface URL (typically port 443 or 8080) and verify the login page loads or check the server configuration for Web UI enablement
    Affected if Web UI is accessible and users can authenticate
  3. Verify authentication is configured
    Check if Aspera Faspex has user authentication enabled (local users, LDAP, or SSO) in the admin settings
    Affected if Authenticated users can access the Web UI to create or view content

Your environment is affected if you are running IBM Aspera Faspex version 5.0.0 through 5.0.14.3 (or any version below 5.0.15) with the Web UI enabled and accessible to authenticated users.

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
Upgrade available Upgrade to 5.0.15 or later
Fixed in 5.0.15
Interim mitigation

Upgrade to IBM Aspera Faspex 5.0.14.4 or later. If no patch is available, implement output encoding and input validation on all user-supplied fields, and consider Content Security Policy headers to mitigate XSS execution.

Recommended fix High confidence

Aspera Faspex 5.0.15

  1. 1. Identify current Aspera Faspex version by checking the application's about or version information page
  2. 2. Create a complete backup of the current Aspera Faspex installation including database and configuration files
  3. 3. Review Aspera upgrade documentation for any pre-upgrade requirements or migration procedures
  4. 4. Download Aspera Faspex version 5.0.15 or later from IBM Aspera's official download portal
  5. 5. Stop the Aspera Faspex services before performing the upgrade
  6. 6. Install the upgrade following IBM's standard upgrade procedures for Aspera Faspex
  7. 7. Verify the upgrade was successful by checking the version information
  8. 8. Test the application functionality to ensure the XSS vulnerability is resolved
Caveat Review release notes for any changes between your current version and 5.0.15; minor version upgrades typically have minimal breaking changes but configuration adjustments may be needed

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

Fix this in Aspera Faspex Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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