IBM Safer Payments could allow an authenticated user to obtain sensitive information
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Not reported
Do first: Apply the patch listed under Evidence.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 8/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
IBM Safer Payments is affected by a flaw that lets a logged-in user obtain sensitive information by sending a crafted set of API requests that decrypt protected data. The attack can be carried out remotely over the network, but it requires the attacker to have a valid user account.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
IBM Safer Payments 6.4.0.00 through 6.4.2.11, 6.5.0.00 through 6.5.0.09, 6.6.0.00 through 6.6.0.07, 6.7.0.00 through 6.7.0.03, and 6.8.0.00 could allow an authenticated user to obtain sensitive information, caused by improper user input validation. By using a set of API requests the user could exploit this vulnerability to decrypt sensitive information.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
What to do
Apply the patch listed under Evidence.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- IBM Safer Payments
From 6.4.0.00 · through 6.4.2.11; From 6.5.0.00 · through 6.5.0.09; From 6.6.0.00 · through 6.6.0.07; From 6.7.0.00 · through 6.7.0.03
Evidence 1
- Patch
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2025-36075
Is CVE-2025-36075 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2025-36075?
Safer Payments: from 6.4.0.00 through 6.4.2.11; from 6.5.0.00 through 6.5.0.09; from 6.6.0.00 through 6.6.0.07; from 6.7.0.00 through 6.7.0.03.Source: cve.now feed data