dbcve.org
Aspera FaspexApplication · Ibm

CVE-2025-3423

MEDIUM · 5.4 CVSS v3.1 Published 2025-04-13
Fix available
A fix is available. Upgrade to 5.0.12 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.0.0 through 5.0.11 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 versions 5.0.0 through 5.0.11 contain a stored cross-site scripting (XSS) vulnerability in the web interface. An authenticated user can inject malicious JavaScript code into web UI fields, which executes in the browsers of other users viewing the injected content, potentially exposing credentials or session tokens within a trusted session.

MitigationUpgrade IBM Aspera Faspex to version 5.0.12 or later to obtain the security fix. Additionally, implement output encoding and input validation for user-supplied content in the web interface as a defense-in-depth measure.

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.12

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. Determine installed Faspex version
    Access the Aspera Faspex admin interface and navigate to the About or System Information section, or run the faspex --version command if available via CLI
    Affected if The installed version falls within 5.0.0 through 5.0.11 inclusive
  2. Verify web interface is enabled
    Check the Aspera Faspex server configuration for web UI settings, typically in the faspex.yml configuration file or admin console under server settings
    Affected if The web interface is accessible and user authentication is enabled
  3. Confirm active user accounts exist
    Review the user management section in the admin console or query the user database to list authenticated users
    Affected if There is at least one authenticated user account in the system who could potentially inject malicious content

If the installed version is 5.0.0 through 5.0.11 and the web interface with user authentication is enabled, the environment is vulnerable to stored XSS attacks.

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.12 or later
Fixed in 5.0.12
Interim mitigation

Upgrade IBM Aspera Faspex to version 5.0.12 or later to obtain the security fix. Additionally, implement output encoding and input validation for user-supplied content in the web interface as a defense-in-depth measure.

Recommended fix High confidence

5.0.12

  1. Verify current installed version of Aspera Faspex using the administrative interface or command line tools
  2. Back up all configuration files, databases, and transfer data according to existing backup procedures
  3. Review IBM Aspera release notes for version 5.0.12 to understand any migration requirements
  4. Download Aspera Faspex version 5.0.12 or later from IBM Fix Central or authorized distribution channels
  5. Execute the upgrade procedure following IBM's official upgrade documentation for Aspera Faspex
  6. After upgrade, verify the application starts successfully and all services are running
  7. Confirm the XSS vulnerability is resolved by logging into the Web UI and verifying the fix
Caveat Review release notes for any configuration changes or migration steps required when upgrading to 5.0.12

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

Fix this in Aspera Faspex Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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