Skip to main content

IBM Aspera Orchestrator CVE-2025-13214

HIGH
SQL Injection (CWE-89)
2025-12-11 psirt@us.ibm.com
8.8
CVSS 3.1 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate with low-privilege account
  2. Exploit
    Submit crafted SQL in request parameter
  3. Execution
    Trigger injection in back-end query
  4. Impact
    Read, modify, or delete database records

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Persistence

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires an authenticated session to IBM Aspera Orchestrator at a low privilege level (CVSS PR:L) - the attacker must possess valid, even limited, application credentials or a valid session, so this is not exploitable by fully anonymous internet attackers. Beyond authentication, no special non-default configuration, platform, or user-interaction requirement is indicated (AC:L, UI:N), meaning any reachable instance running the affected versions 4.0.0 through 4.1.0 is exploitable once the attacker is authenticated. The principal limiting factors are therefore the authentication requirement and network reachability of the Orchestrator instance; the specific vulnerable feature or parameter is not named in the advisory description.

Impact

This is a credible but not emergency-level priority. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N) describes a network-reachable, low-complexity SQL injection requiring only low-privilege authentication (PR:L), with high impact to confidentiality, integrity, and availability (C:H/I:H/A:H) - consistent with an authenticated SQLi that can read, modify, and delete back-end database content. Signals are largely coherent and point to a genuine but contained risk: EPSS is low at 0.36% (28th percentile), indicating no statistical expectation of near-term mass exploitation, and the vulnerability is NOT in CISA KEV, with no public exploit identified at time of analysis. The main caveat is the authentication gate: because PR:L requires an attacker to already hold valid low-privilege credentials or a session, real-world risk is meaningfully lower than the 8.8 base score suggests for internet-exposed, unauthenticated scenarios. There is no conflict between the CVSS vector and the description - both agree on remote, authenticated exploitation. Net: patch on a normal-to-prompt cycle, prioritizing instances exposed to untrusted or broad user populations, but this is not a drop-everything event absent KEV listing or public PoC.

Exploit ScenarioDerived

An attacker with valid low-privilege credentials to IBM Aspera Orchestrator sends specially crafted input through an application parameter that is unsafely concatenated into a SQL query. Because attack complexity is low and no user interaction is needed, the attacker can reliably inject statements to read, alter, or delete back-end database records. No public proof-of-concept exploit has been identified at time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 07, 2026

SQL injection in IBM Aspera Orchestrator 4.0.0 through 4.1.0 lets an authenticated attacker with low privileges send crafted SQL statements to view, add, modify, or delete data in the back-end database. The CVSS v3.1 score is 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning remote exploitation is possible after authentication but not by fully anonymous internet users. No public exploit has been identified at time of analysis, and EPSS is 0.36% (28th percentile), making this a credible but not emergency-level priority.

RemediationAI

No vendor-released patch version is specified in the provided data, so check IBM's advisory at https://www.ibm.com/support/pages/node/7254434 for the latest fixed version or upgrade guidance and apply the vendor-provided update as soon as it is available. Until a fix is applied, restrict network access to IBM Aspera Orchestrator instances to trusted networks or VPN-only access, enforce least privilege, and review low-privileged accounts that could be used for exploitation. Deploy a WAF with SQL injection rules in blocking mode, monitor application and database logs for anomalous SQL query patterns, and rotate credentials for accounts with access to the Orchestrator. Trade-offs: network restrictions may impede legitimate remote users; WAF rules require tuning to avoid blocking valid SQL-like input; least-privilege changes may disrupt existing workflows.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause is CWE-89, improper neutralization of special elements used in an SQL command, which allows attacker-controlled input to alter database queries. IBM Aspera Orchestrator is an enterprise workflow orchestration product with a back-end database, and the CPE cpe:2.3:a:ibm:aspera_orchestrator:*:*:*:*:*:*:*:* identifies the affected product with a wildcard version. The CVSS vector confirms network reachability, low complexity, low privileges (PR:L), no user interaction, and high confidentiality, integrity, and availability impact to the database; the advisory does not name the specific vulnerable endpoint or parameter. Successful exploitation could allow an authenticated low-privileged user to read, insert, modify, or delete database records.

Know when Aspera Orchestrator gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 8.8 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 8.8 HIGH

Network-reachable SQL injection requiring only low-privilege authentication (PR:L) with no user interaction; SQLi permits read/modify/delete of database data, so C/I/A all High.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionNVD

IBM Aspera Orchestrator 4.0.0 through 4.1.0 is vulnerable to SQL injection. A remote attacker could send specially crafted SQL statements, which could allow the attacker to view, add, modify, or delete information in the back-end database.

Executive ViewAI

Why It Matters

IBM Aspera Orchestrator versions 4.0.0 through 4.1.0 contain a high-severity SQL injection vulnerability that allows an authenticated low-privilege user to view, add, modify, or delete data in the back-end database. Organizations using this product for managed file transfers or workflow orchestration face potential data integrity and confidentiality breaches, though no public exploit identified at time of analysis and exploitation requires valid credentials. Leadership should prioritize remediation planning given the lack of a vendor patch and the potential for insider or compromised-account abuse.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis; interim mitigations include restricting network access to trusted management networks, enforcing least privilege for Aspera Orchestrator accounts, monitoring database and application logs for anomalous SQL activity, and deploying web application firewall (WAF) rules to detect and block SQL injection attempts.

Threat Intelligence Overview

EPSS Score
0.4%
Top 72% exploitable
Prevalence
Low
Niche IBM enterprise file-transfer orchestration add-on, limited deployment footprint
Data Quality
3 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.4%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
High

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

Affected Products (CPE)NVD

cpe:2.3:a:ibm:aspera_orchestrator:*:*:*:*:*:*:*:*

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy