dbcve.org
Infosphere Information ServerApplication · Ibm

CVE-2025-0966

HIGH · 7.6 CVSS v3.1 Published 2025-06-25
Fix available
A fix is available. Upgrade to 11.7.1 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable Zero-click

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 InfoSphere Information Server 11.7 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.

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 · moderate confidence

IBM InfoSphere Information Server 11.7 contains a SQL injection vulnerability allowing remote attackers to execute arbitrary SQL statements via specially crafted input. The vulnerability permits viewing, adding, modifying, or deleting data in the back-end database.

MitigationApply IBM's available patch for CVE-2025-0966. If no patch exists, identify and parameterize all user-supplied input in SQL queries, or implement web application firewall rules as temporary mitigation.

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
Infosphere Information ServerApplication
Affected:>= 11.7, < 11.7.1

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
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L

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. Verify IBM InfoSphere Information Server version
    Check the installed version of IBM InfoSphere Information Server by reviewing installation documentation, the version displayed in the administration console, or by querying the product version through its built-in version command or configuration files. Compare this version number against the affected range: 11.7 to versions before 11.7.1.
    Affected if The installed version is 11.7 or any version between 11.7 and 11.7.1 (exclusive of 11.7.1).
  2. Confirm web interface exposure
    Determine whether the IBM InfoSphere Information Server web console or API endpoints are accessible from the network. This vulnerability is exploitable through specially crafted input sent to web-facing components.
    Affected if The web console or any REST/API endpoints of InfoSphere are exposed to untrusted networks without proper network segmentation or authentication layers.
  3. Review application logs for SQL syntax anomalies
    Examine IBM InfoSphere Information Server logs (typically found in the product's logging directory) for entries containing unusual SQL syntax, unexpected WHERE clauses, UNION SELECT statements, or SQL keywords (DROP, DELETE, INSERT, UPDATE) in request parameters where they would not normally appear.
    Affected if Log analysis reveals SQL injection payloads or abnormal SQL patterns in request parameters.
  4. Check for unauthorized database modifications
    Audit the back-end database (DB2, Oracle, or other supported databases) for unexpected changes to schema, new stored procedures, or data modifications occurring at unusual times or from unexpected sources.
    Affected if Database contains unauthorized changes, new objects, or data alterations that were not initiated by known legitimate processes.

A user is affected if their IBM InfoSphere Information Server installation is version 11.7 through any version prior to 11.7.1 and the web interface is accessible, with any evidence of SQL injection attempts or unauthorized database access in logs or the database itself.

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 11.7.1 or later
Fixed in 11.7.1
Interim mitigation

Apply IBM's available patch for CVE-2025-0966. If no patch exists, identify and parameterize all user-supplied input in SQL queries, or implement web application firewall rules as temporary mitigation.

Recommended fix High confidence

11.7.1

  1. Review IBM InfoSphere Information Server 11.7.1 installation and upgrade documentation on IBM Support
  2. Perform a complete backup of the existing InfoSphere Information Server 11.7 installation including all databases, configuration files, and metadata
  3. Stop all InfoSphere services and components before beginning the upgrade
  4. Download IBM InfoSphere Information Server version 11.7.1 from IBM Fix Central or the IBM Passport Advantage site
  5. Execute the upgrade installer following IBM's documented upgrade procedures for your platform
  6. After upgrade completion, restart all InfoSphere services
  7. Verify the installation was successful by checking version information and ensuring all components are operational
  8. Test the previously vulnerable functionality to confirm the SQL injection is remediated
Caveat Review IBM 11.7.1 release notes for any deprecated features, compatibility changes, or migration requirements specific to your environment

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

Fix this in Infosphere Information Server Scoped from the published advisory
  • Consultation16.0 h
  • Implementation24.0 h
  • Testing20.0 h
  • Review / QA12.0 h
72.0 hours of engineering $12,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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