https://patchthecve.com/CVEs with upgrade or downgrade fix stepshttps://patchthecve.com/cve/CVE-2025-12737.htmlhttps://patchthecve.com/cve/CVE-2025-12737.htmlMon, 19 Oct 2026 22:10:00 +0000HIGH 8.4: The administrative operations within the Carbon Console do not adequately validate specific user-supplied input. This oversight allows a malicious actor with administrative privileges to inject and execute arbitrary code remotely. Successful exploitation enables a threat actor with administrative phttps://patchthecve.com/cve/CVE-2026-0637.htmlhttps://patchthecve.com/cve/CVE-2026-0637.htmlWed, 12 Aug 2026 19:29:05 +0000MEDIUM 4.4: When an Event Publisher output adapter is configured with irrelevant properties, the affected products log these properties. This logging occurs without sufficient validation or sanitization of the property values. A malicious actor with access to the 'wso2carbon' log files could retrieve sensitivehttps://patchthecve.com/cve/CVE-2025-15039.htmlhttps://patchthecve.com/cve/CVE-2025-15039.htmlTue, 29 Sep 2026 14:10:00 +0000CRITICAL 9.4: The Conditional Authentication (Adaptive Authentication) script does not correctly enforce the completion of all required authentication steps when a specific multi-step pattern involving certain authenticators is configured. This allows an attacker to bypass intermediate authentication challenges bhttps://patchthecve.com/cve/CVE-2025-13736.htmlhttps://patchthecve.com/cve/CVE-2025-13736.htmlTue, 29 Sep 2026 14:10:00 +0000LOW 3.7: When Multi-Attribute Login is enabled, the login interface fails to consistently mask the existence of user accounts. For valid users, the server resolves and displays their canonical username, while for non-existent users, it echoes the original input. This occurs regardless of the validate_usernamhttps://patchthecve.com/cve/CVE-2025-13394.htmlhttps://patchthecve.com/cve/CVE-2025-13394.htmlTue, 29 Sep 2026 14:10:00 +0000MEDIUM 5.4: 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 mechanishttps://patchthecve.com/cve/CVE-2024-8995.htmlhttps://patchthecve.com/cve/CVE-2024-8995.htmlThu, 13 Aug 2026 13:18:42 +0000MEDIUM 4.9: Unused authorization codes issued to deleted users are not being properly invalidated or removed from the system. This allows for the persistence of these codes, enabling them to be potentially reused. If an attacker possesses both the authorization code and the associated client credentials (clienhttps://patchthecve.com/cve/CVE-2024-6832.htmlhttps://patchthecve.com/cve/CVE-2024-6832.htmlSun, 09 Aug 2026 14:14:01 +0000MEDIUM 5.9: The account locking mechanism fails to trigger when secondary user stores are inaccessible. The software does not maintain a consistent state for account locking if it cannot reach all configured user stores, allowing an attacker to repeatedly attempt authentication with invalid credentials without https://patchthecve.com/cve/CVE-2024-10302.htmlhttps://patchthecve.com/cve/CVE-2024-10302.htmlSun, 09 Aug 2026 14:25:39 +0000MEDIUM 4.0: The user self-signup flow in multiple WSO2 products fails to adequately validate user-supplied input. This weakness allows arbitrary unvalidated data to be included within user claims, which are then used by downstream processes. Allowing unvalidated input into user claims can lead to various secur