CVE-2025-14790 | IBM InfoSphere Information Server up to 11.7.1.6 insufficiently protected credentials
VulDBArchived Mar 26, 2026✓ Full text saved
A vulnerability described as problematic has been identified in IBM InfoSphere Information Server up to 11.7.1.6 . This affects an unknown part. Such manipulation leads to insufficiently protected credentials. This vulnerability is listed as CVE-2025-14790 . The attack may be performed from remote. There is no available exploit. Upgrading the affected component is recommended.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-353499 · CVE-2025-14790 · GCVE-0-2025-14790
IBM INFOSPHERE INFORMATION SERVER UP TO 11.7.1.6 INSUFFICIENTLY PROTECTED CREDENTIALS
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
5.3 $0-$5k 2.10+
Summaryinfo
A vulnerability classified as problematic has been found in IBM InfoSphere Information Server up to 11.7.1.6. This vulnerability affects unknown code. Performing a manipulation results in insufficiently protected credentials. This vulnerability is cataloged as CVE-2025-14790. It is possible to initiate the attack remotely. There is no exploit available. It is recommended to upgrade the affected component.
Detailsinfo
A vulnerability was found in IBM InfoSphere Information Server up to 11.7.1.6. It has been classified as problematic. This affects some unknown processing. The manipulation with an unknown input leads to a insufficiently protected credentials vulnerability. CWE is classifying the issue as CWE-522. The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval. This is going to have an impact on confidentiality. The summary by CVE is:
IBM InfoSphere Information Server 11.7.0.0 through 11.7.1.6 could allow an attacker to obtain sensitive information due to insufficiently protected credentials.
It is possible to read the advisory at ibm.com. This vulnerability is uniquely identified as CVE-2025-14790 since 12/16/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 03/25/2026). The attack technique deployed by this issue is T1552 according to MITRE ATT&CK.
Upgrading eliminates this vulnerability.
Productinfo
Type
Reporting Software
Vendor
IBM
Name
InfoSphere Information Server
Version
11.7.1.0
11.7.1.1
11.7.1.2
11.7.1.3
11.7.1.4
11.7.1.5
11.7.1.6
License
commercial
Website
Vendor: https://www.ibm.com/
CPE 2.3info
🔒
🔒
🔒
CPE 2.2info
🔒
🔒
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv3info
VulDB Meta Base Score: 5.4
VulDB Meta Temp Score: 5.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.5
CNA Vector (ibm): 🔒
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Insufficiently protected credentials
CWE: CWE-522
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: Upgrade
Status: 🔍
0-Day Time: 🔒
Timelineinfo
12/16/2025 CVE reserved
03/25/2026 +99 days Advisory disclosed
03/25/2026 +0 days VulDB entry created
03/25/2026 +0 days VulDB entry last update
Sourcesinfo
Vendor: ibm.com
Advisory: ibm.com
Status: Confirmed
CVE: CVE-2025-14790 (🔒)
GCVE (CVE): GCVE-0-2025-14790
GCVE (VulDB): GCVE-100-353499
Entryinfo
Created: 03/25/2026 23:00
Changes: 03/25/2026 23:00 (63)
Complete: 🔍
Cache ID: 99:7DF:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸