CVE-2025-14912 | IBM InfoSphere Information Server up to 11.7.1.6 server-side request forgery
VulDBArchived Mar 26, 2026✓ Full text saved
A vulnerability was found in IBM InfoSphere Information Server up to 11.7.1.6 . It has been declared as critical . The impacted element is an unknown function. Such manipulation leads to server-side request forgery. This vulnerability is uniquely identified as CVE-2025-14912 . The attack can be launched remotely. No exploit exists. It is recommended to upgrade the affected component.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-353493 · CVE-2025-14912 · GCVE-0-2025-14912
IBM INFOSPHERE INFORMATION SERVER UP TO 11.7.1.6 SERVER-SIDE REQUEST FORGERY
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
5.7 $0-$5k 1.40+
Summaryinfo
A vulnerability was found in IBM InfoSphere Information Server up to 11.7.1.6. It has been rated as critical. This affects an unknown function. Performing a manipulation results in server-side request forgery. This vulnerability was named CVE-2025-14912. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is advised.
Detailsinfo
A vulnerability classified as critical has been found in IBM InfoSphere Information Server up to 11.7.1.6. This affects an unknown function. The manipulation with an unknown input leads to a server-side request forgery vulnerability. CWE is classifying the issue as CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
IBM InfoSphere Information Server 11.7.0.0 through 11.7.1.6 is vulnerable to server-side request forgery (SSRF). This may allow an authenticated attacker to send unauthorized requests from the system, potentially leading to network enumeration or facilitating other attacks.
The advisory is shared at ibm.com. This vulnerability is uniquely identified as CVE-2025-14912 since 12/18/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 03/25/2026).
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.9
VulDB Meta Temp Score: 5.7
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.4
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: Server-side request forgery
CWE: CWE-918
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/18/2025 CVE reserved
03/25/2026 +97 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-14912 (🔒)
GCVE (CVE): GCVE-0-2025-14912
GCVE (VulDB): GCVE-100-353493
Entryinfo
Created: 03/25/2026 23:00
Changes: 03/25/2026 23:00 (64)
Complete: 🔍
Cache ID: 99:3C1:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸