# CVE-2025-14260: Server Side Request Forgery in Multiple WSO2 Products Allows Access to Internal and External Resources


- **Severity:** High 8.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-mqxf-9g4h-p3qm

## What is CVE-2025-14260?

CVE-2025-14260 is a high-severity vulnerability in WSO2 SAML2 SSO Authenticator UI Bundle, published on 28 Oct 2026. 

### Official 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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2025-14260?


## How do I fix CVE-2025-14260?

No fix has been published for CVE-2025-14260 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-14260 being exploited?

There is no known exploitation of CVE-2025-14260 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-14260 and fix it if it is affected.

What it is: CVE-2025-14260 is a high-severity vulnerability in WSO2 SAML2 SSO Authenticator UI Bundle, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2025-14260 in the wild and no public exploit code.

Affected product: WSO2 SAML2 SSO Authenticator UI Bundle. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-14260/ (Markdown: https://insights.sbomify.com/CVE-2025-14260/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-14260
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-14260
- OSV: https://osv.dev/vulnerability/CVE-2025-14260

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-14260/
Summaries are generated and may contain mistakes; the official description above is the record.