HighCVE-2025-14260

    WSO2 API Manager: Server-Side Request Forgery (SSRF) (CVE-2025-14260)

    Published Last modified Sources: CVE.org

    What is affected, what to do

    Due to the improper implementation of access control rules, the WSO2 product accepts user-supplied input related to resource location without enforcing expected validation constraints. This can be exploited by an unauthenticated actor to direct the server to make requests to arbitrary network locations.

    Update WSO2 Identity Server to version 7.0.0.134, WSO2 API Manager to version 3.1.0.354, WSO2 API Manager to version 3.2.0.458.

    Affected
    • WSO2 Identity Server lt 7.0.0..7.0.0.134
    • WSO2 API Manager lt 3.1.0..3.1.0.354
    • WSO2 API Manager lt 3.2.0..3.2.0.458
    • WSO2 API Manager lt 3.2.1..3.2.1.99
    • WSO2 API Manager lt 4.0.0..4.0.0.379
    • WSO2 API Manager lt 4.1.0..4.1.0.265
    • WSO2 API Manager lt 4.2.0..4.2.0.205
    • WSO2 API Manager lt 4.3.0..4.3.0.115
    • WSO2 API Manager lt 4.4.0..4.4.0.79
    • WSO2 Identity Server as Key Manager lt 5.10.0..5.10.0.374
    • WSO2 Open Banking AM lt 2.0.0..2.0.0.403
    • WSO2 Open Banking IAM lt 2.0.0..2.0.0.423
    • WSO2 Identity Server lt 5.10.0..5.10.0.383
    • WSO2 Identity Server lt 5.11.0..5.11.0.430
    • WSO2 Identity Server lt 6.0.0..6.0.0.256
    • WSO2 Identity Server lt 6.1.0..6.1.0.257
    • WSO2 SAML2 SSO Authenticator UI Bundle lt 5.5.0..5.5.0.2
    • WSO2 SAML2 SSO Authenticator UI Bundle lt 5.5.2..5.5.2.5
    • WSO2 SAML2 SSO Authenticator UI Bundle lt 5.5.9..5.5.9.4
    • WSO2 SAML2 SSO Authenticator UI Bundle lt 5.5.10..5.5.10.1
    • WSO2 SAML2 SSO Authenticator UI Bundle lt 5.6.4..5.6.4.1
    • WSO2 SAML2 SSO Authenticator UI Bundle lt 5.7.2..5.7.2.1
    • WSO2 SAML2 SSO Authenticator UI Bundle lt 5.8.3..5.8.3.1
    • WSO2 SAML2 SSO Authenticator UI Bundle lt 5.8.7..5.8.7.2
    • WSO2 SAML2 SSO Authenticator UI Bundle lt 5.9.4..5.9.4.2
    • WSO2 Carbon UI lt 4.6.0..4.6.0.2300
    • WSO2 Carbon UI lt 4.6.1..4.6.1.165
    • WSO2 Carbon UI lt 4.6.3..4.6.3.46
    • WSO2 Carbon UI lt 4.6.4..4.6.4.28
    • WSO2 Carbon UI lt 4.7.1..4.7.1.79
    • WSO2 Carbon UI lt 4.8.1..4.8.1.50
    • WSO2 Carbon UI lt 4.9.0..4.9.0.107
    • WSO2 Carbon UI lt 4.9.26..4.9.26.37
    • WSO2 Carbon UI lt 4.9.27..4.9.27.24
    • WSO2 Carbon UI lt 4.10.9..4.10.9.77
    Fixed in
    • WSO2 Identity Server 7.0.0.134
    • WSO2 API Manager 3.1.0.354
    • WSO2 API Manager 3.2.0.458
    • WSO2 API Manager 3.2.1.99
    • WSO2 API Manager 4.0.0.379
    • WSO2 API Manager 4.1.0.265
    • WSO2 API Manager 4.2.0.205
    • WSO2 API Manager 4.3.0.115
    • WSO2 API Manager 4.4.0.79
    • WSO2 Identity Server as Key Manager 5.10.0.374
    • WSO2 Open Banking AM 2.0.0.403
    • WSO2 Open Banking IAM 2.0.0.423
    • WSO2 Identity Server 5.10.0.383
    • WSO2 Identity Server 5.11.0.430
    • WSO2 Identity Server 6.0.0.256
    • WSO2 Identity Server 6.1.0.257
    • WSO2 SAML2 SSO Authenticator UI Bundle 5.5.0.2
    • WSO2 SAML2 SSO Authenticator UI Bundle 5.5.2.5
    • WSO2 SAML2 SSO Authenticator UI Bundle 5.5.9.4
    • WSO2 SAML2 SSO Authenticator UI Bundle 5.5.10.1
    • WSO2 SAML2 SSO Authenticator UI Bundle 5.6.4.1
    • WSO2 SAML2 SSO Authenticator UI Bundle 5.7.2.1
    • WSO2 SAML2 SSO Authenticator UI Bundle 5.8.3.1
    • WSO2 SAML2 SSO Authenticator UI Bundle 5.8.7.2
    • WSO2 SAML2 SSO Authenticator UI Bundle 5.9.4.2
    • WSO2 Carbon UI 4.6.0.2300
    • WSO2 Carbon UI 4.6.1.165
    • WSO2 Carbon UI 4.6.3.46
    • WSO2 Carbon UI 4.6.4.28
    • WSO2 Carbon UI 4.7.1.79
    • WSO2 Carbon UI 4.8.1.50
    • WSO2 Carbon UI 4.9.0.107
    • WSO2 Carbon UI 4.9.26.37
    • WSO2 Carbon UI 4.9.27.24
    • WSO2 Carbon UI 4.10.9.77

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    8.3

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v3

    8.3

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: CVE.org

    —

    EPSS score

    No value is available for this vulnerability.

    Show all metrics
    Severity
    High
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    71.50 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    8.3 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    8.3
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CISA assessment (SSVC)
    Exploitation: none known · not automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 29 October 2026
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-918

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    Due to the improper implementation of access control rules, the WSO2 product accepts user-supplied input related to resource location without enforcing expected validation constraints. This can be exploited by an unauthenticated actor to direct the server to make requests to arbitrary network locations. Exploiting this vulnerability allows a malicious actor to access both internal and external resources, available through the network or filesystem, that are reachable by the WSO2 product. This could potentially lead to unauthorized access to sensitive data and systems.

    Source: NVD (NIST), cvelistv5

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    WSO2SAML2 SSO Authenticator UI Bundle
    • 5.8.3 – < 5.8.3.1
    • 5.8.7 – < 5.8.7.2
    • 5.5.10 – < 5.5.10.1
    • 5.5.2 – < 5.5.2.5
    • 5.5.0 – < 5.5.0.2
    • 5.5.9 – < 5.5.9.4
    • 5.9.4 – < 5.9.4.2
    • 5.6.4 – < 5.6.4.1
    • 5.7.2 – < 5.7.2.1
    • 5.8.3.1
    • 5.8.7.2
    • 5.5.10.1
    • 5.5.2.5
    • 5.5.0.2
    • 5.5.9.4
    • 5.9.4.2
    • 5.6.4.1
    • 5.7.2.1
    WSO2WSO2 API Manager
    • 3.2.1 – < 3.2.1.99
    • 3.2.0 – < 3.2.0.458
    • 3.1.0 – < 3.1.0.354
    • 4.2.0 – < 4.2.0.205
    • 4.3.0 – < 4.3.0.115
    • 4.0.0 – < 4.0.0.379
    • 4.1.0 – < 4.1.0.265
    • 4.4.0 – < 4.4.0.79
    • 3.2.1.99
    • 3.2.0.458
    • 3.1.0.354
    • 4.2.0.205
    • 4.3.0.115
    • 4.0.0.379
    • 4.1.0.265
    • 4.4.0.79
    WSO2WSO2 Carbon UI
    • 4.6.3 – < 4.6.3.46
    • 4.9.27 – < 4.9.27.24
    • 4.7.1 – < 4.7.1.79
    • 4.8.1 – < 4.8.1.50
    • 4.9.26 – < 4.9.26.37
    • 4.6.0 – < 4.6.0.2300
    • 4.10.9 – < 4.10.9.77
    • 4.6.1 – < 4.6.1.165
    • 4.6.4 – < 4.6.4.28
    • 4.9.0 – < 4.9.0.107
    • 4.6.3.46
    • 4.9.27.24
    • 4.7.1.79
    • 4.8.1.50
    • 4.9.26.37
    • 4.6.0.2300
    • 4.10.9.77
    • 4.6.1.165
    • 4.6.4.28
    • 4.9.0.107
    WSO2WSO2 Identity Server
    • 6.1.0 – < 6.1.0.257
    • 5.11.0 – < 5.11.0.430
    • 5.10.0 – < 5.10.0.383
    • 7.0.0 – < 7.0.0.134
    • 6.0.0 – < 6.0.0.256
    • 6.1.0.257
    • 5.11.0.430
    • 5.10.0.383
    • 7.0.0.134
    • 6.0.0.256
    WSO2WSO2 Identity Server as Key Manager
    • 5.10.0 – < 5.10.0.374
    • 5.10.0.374
    WSO2WSO2 Open Banking AM
    • 2.0.0 – < 2.0.0.403
    • 2.0.0.403
    WSO2WSO2 Open Banking IAM
    • 2.0.0 – < 2.0.0.423
    • 2.0.0.423

    Vendors and products

    Weakness classes (CWE)

    • CWE-918Server-Side Request Forgery (SSRF)

      Base

      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.

      Entry at MITRE CWE-918

    References & sources

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: none known, automatable: no

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      SSVC assessmentadded
      —
      {"id":"CVE-2025-14260","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-10-29T01:52:09.688697Z"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    2. Receiveded10eef1…

      CVSS V3.1: AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

      Weakness type: CWE-918

      Description added or changed

      Show 5 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      Due to the improper implementation of access control rules, the WSO2 product accepts user-supplied input related to resource location without enforcing expected validation constraints. This can be exploited by an unauthenticated actor to direct the server to make requests to arbitrary network locations. Exploiting this vulnerability allows a malicious actor to access both internal and external resources, available through the network or filesystem, that are reachable by the WSO2 product. This could potentially lead to unauthorized access to sensitive data and systems.
      CVSSadded
      —
      AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
      Weakness type (CWE)added
      —
      CWE-918
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2025/14xxx/CVE-2025-14260.json">CVE-2025-14260</a>
      Referenceadded
      —
      https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4050/

      Source identifier: ed10eef1-636d-4fbe-9993-6890dfa878f8

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2025-14260
    <a href="https://intel.neosec.eu/en/cve/CVE-2025-14260"><img src="https://intel.neosec.eu/badge/cve/CVE-2025-14260.svg?lang=en" alt="CVE-2025-14260 – NEOSEC Intel" height="20"></a>