# CVE-2025-13394: Cross-Site Request Forgery via Ajax Processor Endpoints in Multiple WSO2 Products Enables Unauthorized Actions > Attackers can trick authenticated users into performing unauthorized actions via CSRF in WSO2 Carbon console if exposed to the internet. - **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** No - **Published:** 6 Aug 2026 - **Updated:** 6 Aug 2026 - **Also known as:** GHSA-8rr2-f52p-r9q3 ## What is CVE-2025-13394? CVE-2025-13394 is a medium-severity vulnerability in Wso2 Api Manager, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description The Ajax processor within the Carbon console fails to adequately protect state-changing operations from Cross-Site Request Forgery (CSRF) attacks. Specifically, it utilizes the HTTP GET method for these operations, and while the SameSite=Lax cookie attribute is employed for mitigation, this mechanism is bypassed as it permits cookies to be sent with cross-origin top-level navigation requests, including GET requests. This allows an attacker to trick an authenticated user's browser into unknowingly executing unintended actions. An attacker can exploit this vulnerability to perform unauthorized state-altering requests on behalf of authenticated users. This could lead to consequences such as data modification, account changes, or other actions that could result in data compromise or loss of user control over their account. However, this attack is only feasible if the Carbon console and related services are exposed to the public internet, which is not recommended according to WSO2's security guidelines. Weakness: CWE-352 (Cross-Site Request Forgery) ## Which versions are affected by CVE-2025-13394? It affects 9 products. Products: Wso2 Api Control Plane, Wso2 Api Manager, Wso2 Enterprise Integrator, Wso2 Identity Server, Wso2 Identity Server as Key Manager, Wso2 Open Banking Am, Wso2 Open Banking Iam, Wso2 Traffic Manager, Wso2 Universal Gateway. ## How do I fix CVE-2025-13394? No fix has been published for CVE-2025-13394 yet. Limit exposure of the affected software until one is available. ## Is CVE-2025-13394 being exploited? There is no known exploitation of CVE-2025-13394 in the wild and no public exploit code. ## Other vulnerabilities in Wso2 Api Manager - [CVE-2026-5430](https://insights.sbomify.com/CVE-2026-5430/): WSO2 Multiple Products Path Traversal Vulnerability (critical 10.0, exploited in the wild) - [CVE-2026-1728](https://insights.sbomify.com/CVE-2026-1728/): Privilege Escalation via System REST APIs in Multiple WSO2 Products Permits Admin Account Takeover (critical 9.8) - [CVE-2025-9312](https://insights.sbomify.com/CVE-2025-9312/): Improper Certificate-Based Authentication Enforcement in Multiple WSO2 Products (critical 9.8) - [CVE-2025-10611](https://insights.sbomify.com/CVE-2025-10611/): Potential Broken Access Control in Multiple WSO2 Products via System REST APIs (critical 9.8) - [CVE-2025-9152](https://insights.sbomify.com/CVE-2025-9152/): Improper Privilege Management in Multiple WSO2 API Manager via keymanager-operations DCR Endpoint (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-13394 and fix it if it is affected. What it is: CVE-2025-13394 is a medium-severity vulnerability in Wso2 Api Manager, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2025-13394 in the wild and no public exploit code. Affected product: Wso2 Api Manager. 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-13394/ (Markdown: https://insights.sbomify.com/CVE-2025-13394/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-13394 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-13394 - OSV: https://osv.dev/vulnerability/CVE-2025-13394 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-13394/ Summaries are generated and may contain mistakes; the official description above is the record.