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-14779.htmlhttps://patchthecve.com/cve/CVE-2025-14779.htmlTue, 29 Sep 2026 19:10:00 +0000LOW 3.8: The Secret Type Management REST API does not correctly isolate access controls when deleting a secret type. The on-delete cascade logic, when triggered, fails to enforce organizational boundaries, leading to the removal of secrets associated with that type across all organizations. Exploitation of https://patchthecve.com/cve/CVE-2025-13909.htmlhttps://patchthecve.com/cve/CVE-2025-13909.htmlTue, 29 Sep 2026 14:10:00 +0000MEDIUM 4.3: The system accepts authentication requests without sufficient validation to enforce tenant isolation when using Email OTP, SMS OTP, or Magic Link as first-factor authenticators. This failure to adequately separate user data between tenants can lead to the exposure of personally identifiable informathttps://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-2025-12627.htmlhttps://patchthecve.com/cve/CVE-2025-12627.htmlTue, 29 Sep 2026 14:10:00 +0000LOW 2.4: The user impersonation flow in WSO2 Identity Server fails to properly manage refresh tokens associated with impersonated sessions. This allows an attacker who has obtained an access token for an impersonated user to leverage the refresh token grant to obtain new access tokens, extending their abilithttps://patchthecve.com/cve/CVE-2025-11850.htmlhttps://patchthecve.com/cve/CVE-2025-11850.htmlTue, 29 Sep 2026 14:10:00 +0000MEDIUM 4.3: When secondary user stores are configured, the implicit-association resolver incorrectly initializes from a secondary user store and bypasses the primary user store during search and uniqueness checks. This allows a subject to be associated with an unintended local account if the same lookup claim (https://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 securhttps://patchthecve.com/cve/CVE-2026-2445.htmlhttps://patchthecve.com/cve/CVE-2026-2445.htmlWed, 19 Aug 2026 19:29:34 +0000MEDIUM 6.1: The affected product accepts user-supplied input within a URL parameter without enforcing expected sanitization or encoding before rendering it within the response. This condition allows for the injection of malicious JavaScript payloads. An attacker can leverage this vulnerability to cause the usehttps://patchthecve.com/cve/CVE-2025-8591.htmlhttps://patchthecve.com/cve/CVE-2025-8591.htmlTue, 06 Oct 2026 22:10:00 +0000MEDIUM 6.1: The software accepts user-supplied input via a URL parameter without adequate output encoding before reflecting it back to the user's browser. This condition allows an attacker to inject malicious script content into pages served by the application. By leveraging this weakness, an attacker can caushttps://patchthecve.com/cve/CVE-2024-1248.htmlhttps://patchthecve.com/cve/CVE-2024-1248.htmlThu, 09 Jul 2026 18:47:41 +0000MEDIUM 4.8: The silent Just-In-Time (JIT) provisioning feature in federated authentication implementations fails to properly segregate user roles during account creation when a federated user shares a username with a local user. This allows the provisioning process to overwrite existing roles of local users withttps://patchthecve.com/cve/CVE-2025-13475.htmlhttps://patchthecve.com/cve/CVE-2025-13475.htmlTue, 06 Oct 2026 22:10:00 +0000LOW 3.5: In multi-tenanted deployments, the application consent management mechanism fails to correctly isolate consent scopes between tenants. Consent granted by a user for a specific SaaS application within one tenant can be incorrectly applied to SaaS applications with the same name in other tenants, lead