CVE-2025-36262

CVE-2025-36262 is a medium-severity vulnerability in Ibm Planning Analytics Local with a CVSS 3.x base score of 4.9. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-1286.

Key facts

Description

IBM Planning Analytics Local 2.0.0 through 2.0.106 and 2.1.0 through 2.1.13 could allow a malicious privileged user to bypass the UI to gain unauthorized access to sensitive information due to the improper validation of input.

Frequently asked questions

What is CVE-2025-36262?
IBM Planning Analytics Local 2.0.0 through 2.0.106 and 2.1.0 through 2.1.13 could allow a malicious privileged user to bypass the UI to gain unauthorized access to sensitive information due to the improper validation of input.
How severe is CVE-2025-36262?
CVE-2025-36262 has a CVSS 3.x base score of 4.9, rated medium severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2025-36262 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (20th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-36262?
CVE-2025-36262 affects Ibm Planning Analytics Local. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-36262?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-36262 have an EU (EUVD) identifier?
Yes. CVE-2025-36262 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-31774.
When was CVE-2025-36262 published?
CVE-2025-36262 was published on 2025-09-30 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Ibm Planning Analytics Local

All CVEs affecting Ibm Planning Analytics Local →

Other CWE-1286 vulnerabilities

Browse all CWE-1286 vulnerabilities →