Browser code execution via HTML injection
Published May 22, 2025 · Updated Aug 26, 2025
HTML injection in IBM Aspera Faspex 5.0.0 through 5.0.12 allows remote authenticated users to execute browser code through stored input. IBM identifies no affected field, request, or rendering function, so the exact input-handling failure is undisclosed. A low-privilege account and a victim viewing the injected content are required; execution remains within the hosting site's browser context.
Summary
What happened
HTML injection in IBM Aspera Faspex 5.0.0 through 5.0.12 allows remote authenticated users to execute browser code through stored input. IBM identifies no affected field, request, or rendering function, so the exact input-handling failure is undisclosed. A low-privilege account and a victim viewing the injected content are required; execution remains within the hosting site's browser context.
The record
- CVE
- CVE-2025-33138
- Published
- May 22, 2025
- Updated
- Aug 26, 2025
- Vendor
- IBM
- Product
- IBM Aspera Faspex
- Classifications
- CWE-80, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 22, 2025CVE publishedPublication date reported by the CVE source.
- Aug 26, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.0.0 <=5.0.12
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo