dbcve.org
Aspera FaspexApplication · Ibm

CVE-2025-36230

MEDIUM · 5.4 CVSS v3.1 Published 2025-12-26
Fix available
A fix is available. Upgrade to 5.0.14.2 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.1 is vulnerable to HTML injection. A remote attacker could inject malicious HTML code, which when viewed, would be executed in the victim's Web browser within the security context of the hosting site.

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.1 contains an HTML injection vulnerability that allows remote attackers to inject malicious HTML code into web pages served by the application. When victims view the crafted content, the injected HTML executes within the security context of the hosting site, potentially leading to session hijacking, credential theft, or defacement.

MitigationApply the vendor patch when available; until then, implement strict input validation and output encoding on all user-supplied fields to prevent HTML injection. Consider deploying a WAF rule to detect and block injection attempts.

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

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. Locate the installed version of IBM Aspera Faspex
    Access the Faspex administration interface and navigate to the About or System Information page. Alternatively, check the version using the faspex CLI tool if available: 'faspex --version' or inspect the installation manifest files in the application directory.
    Affected if The displayed version falls within 5.0.0 through 5.0.14.1
  2. Verify the web application is accessible
    Confirm that the Faspex web interface is reachable by accessing the base URL (typically https://your-faspex-host/faspex) in a browser. HTML injection vulnerabilities affect only users who interact with the web-facing application.
    Affected if The web interface is active and users can log in to view content
  3. Identify exposed user input fields
    Log into Faspex as a standard user and examine common input areas: the file transfer description/comment fields, user profile fields (display name, email), package metadata, and any messaging or notes fields.
    Affected if User-controllable input fields exist in the web interface that could accept and store arbitrary HTML content
  4. Check for existing injection artifacts in logs
    Review Faspex server logs (typically located in the logs/ directory under the Faspex installation) for unusual HTML or script tags in user-submitted fields, particularly in transfer history or package metadata entries.
    Affected if Logs contain unexpected HTML tags (<script>, <iframe>, <img>, etc.) in user input fields, indicating possible exploitation attempts

You are affected if your installed IBM Aspera Faspex version is 5.0.0 through 5.0.14.1 and the web interface is active with user-accessible input fields.

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.14.2 or later
Fixed in 5.0.14.2
Interim mitigation

Apply the vendor patch when available; until then, implement strict input validation and output encoding on all user-supplied fields to prevent HTML injection. Consider deploying a WAF rule to detect and block injection attempts.

Recommended fix High confidence

5.0.14.2 or later

  1. Verify current Aspera Faspex version by accessing the admin console or checking the installed package
  2. Review current system backup and ensure recent data backups are completed
  3. Schedule maintenance window for the upgrade procedure
  4. Download Aspera Faspex version 5.0.14.2 or later from IBM Aspera official channels
  5. Stop Aspera Faspex services before initiating the upgrade
  6. Run the upgrade installer following standard IBM Aspera installation procedures
  7. After upgrade completion, verify that services start successfully
  8. Log into the admin console and confirm the version displays as 5.0.14.2 or later
Caveat Review IBM release notes for 5.0.14.2 for any configuration or compatibility changes from prior versions

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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