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.
Published: 2026-08-06
Score: 5.4 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The Ajax processor in WSO2's Carbon consoles processes state‑changing operations using the HTTP GET method. The same‑site cookie attribute is set to Lax, but this does not stop GET requests from being sent with cross‑origin top‑level navigation. A malicious site can therefore trick a logged‑in user’s browser into performing unintended actions. This results in unauthorized modifications such as data tampering, account changes, or loss of user control. The vulnerability is a classic CSRF flaw, identified as CWE‑352.

Affected Systems

The flaw affects a broad set of WSO2 products, including the API Control Plane, API Manager, various Carbon consoles (Command Mediator UI, Event UI, Governance UI, Identity Management UI, etc.), Enterprise Integrator, Identity Server, Open Banking AM/IAM, Stratos components, Traffic Manager, Universal Gateway, and others. Version specifics are not provided in the CNA data, so verification of affected releases should be performed on each product by consulting the vendor’s advisory.

Risk and Exploitability

With a CVSS score of 5.4, the issue is considered a moderate risk. No EPSS score is reported, and the vulnerability is not listed in CISA’s KEV catalog. The attack is feasible only when the Carbon console or related services are exposed to the public internet, a configuration that WSO2 advises against. An attacker would need to host a malicious page that initiates a cross‑origin GET request, causing the victim’s browser to send the stored authentication cookie and trigger the state‑changing operation.

Generated by OpenCVE AI on August 6, 2026 at 09:22 UTC.

Remediation

Vendor Solution

Follow the instructions given on https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4800/#solution


OpenCVE Recommended Actions

  • Apply the patch or upgrade described in the WSO2 advisory at the supplied URL
  • Restrict access to all Carbon consoles and related services so they are not publicly reachable
  • Implement or enforce CSRF tokens for all state‑changing operations and transition vulnerable GET actions to POST where feasible

Generated by OpenCVE AI on August 6, 2026 at 09:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 06 Aug 2026 13:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Thu, 06 Aug 2026 08:15:00 +0000

Type Values Removed Values Added
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.
Title Cross-Site Request Forgery via Ajax Processor Endpoints in Multiple WSO2 Products Enables Unauthorized Actions
Weaknesses CWE-352
References
Metrics cvssV3_1

{'score': 5.4, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: WSO2

Published:

Updated: 2026-08-06T12:32:29.065Z

Reserved: 2025-11-19T06:17:35.259Z

Link: CVE-2025-13394

cve-icon Vulnrichment

Updated: 2026-08-06T12:32:26.203Z

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-06T09:30:02Z

Weaknesses
  • CWE-352

    Cross-Site Request Forgery (CSRF)