CVE-2024-4457 — Remote Code Execution via JDBC User Store Configuration in Multiple WSO2 Products Allows Arbitrary Code Execution
The Management Console fails to properly validate input related to the configuration of JDBC user stores. This weakness allows an attacker to supply specially crafted input that can lead to the execution of arbitrary code on the affected server. Successful exploitation of this vulnerability enables an attacker to execute arbitrary code on the server with the privileges of the WSO2 product. This could lead to a full compromise of the system.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (WSO2 Api Manager, WSO2 Enterprise Integrator, WSO2 Identity Server…).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| WSO2 | Api Manager | ≥ 3.2.0 and < 3.2.0.365≥ 3.2.1 and < 3.2.1.19≥ 4.0.0 and < 4.0.0.308≥ 4.1.0 and < 4.1.0.170≥ 4.2.0 and < 4.2.0.107≥ 4.3.0 and < 4.3.0.21≥ 3.1.0 and < 3.1.0.275 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| WSO2 | Enterprise Integrator | ≥ 6.6.0 and < 6.6.0.204 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| WSO2 | Identity Server | ≥ 5.10.0 and < 5.10.0.296≥ 5.11.0 and < 5.11.0.336≥ 6.0.0 and < 6.0.0.188≥ 6.1.0 and < 6.1.0.148≥ 7.0.0 and < 7.0.0.15 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| WSO2 | Identity Server As Key Manager | ≥ 5.10.0 and < 5.10.0.292 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| WSO2 | Open Banking Am | ≥ 2.0.0 and < 2.0.0.325 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| WSO2 | Open Banking Iam | ≥ 2.0.0 and < 2.0.0.345 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| WSO2 | WSO2 Carbon User Manager Kernel |
≥ 4.5.0 and < 4.5.0.4≥ 4.5.3 and < 4.5.3.34≥ 4.6.0 and < 4.6.0.141≥ 4.6.1 and < 4.6.1.108≥ 4.6.2 and < 4.6.2.610≥ 4.6.3 and < 4.6.3.23≥ 4.6.4 and < 4.6.4.5≥ 4.7.1 and < 4.7.1.51 and 4 more≥ 4.8.1 and < 4.8.1.23≥ 4.9.0 and < 4.9.0.54≥ 4.9.26 and < 4.9.26.13≥ 4.10.9 and < 4.10.9.10 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Look for parameters with command/query metacharacters and unexpected child processes of the service.
Timeline
What happened to this CVE, newest first.
- 2026
- Source status changed · Received → Awaiting Analysis
- Record published
- Affected products added · wso2/wso2 enterprise integrator, wso2/wso2 api manager, wso2/wso2 open banking am, wso2/wso2 open banking iam, wso2/wso2
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 19, 2026 – Oct 19, 2026
- 1× Official description updated · Oct 18, 2026 – Oct 18, 2026
References
5 on the record
- github.com/wso2/carbon-kernel/pull/4067
- github.com/advisories/GHSA-4m8f-7prf-f25h
- security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2023-3
- security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2023-3
- nvd.nist.gov/vuln/detail/CVE-2024-4457
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2025-7203 Sensitive Information Disclosure via Management Console and Product Files in Multiple WSO2 Products Allows Retrieval of Credentials 8h
- Medium CVE-2025-13591 Username Enumeration via Authentication Endpoint in WSO2 Identity Server Allows User Account Discovery 8h
- Medium CVE-2025-13173 Improper Token Revocation via Session-Bound Token Flow in Multiple WSO2 Products Allows Unauthorized Access After Session Termination 8h
- Medium CVE-2025-6623 Stored Cross-Site Scripting via XML Input in Multiple WSO2 Products Allows UI Manipulation and Redirection 8h
- Medium CVE-2025-7043 Refresh Token Misuse via Validation Flaw in Multiple WSO2 Products Enables Unauthorized Resource Consumption 8h
- High CVE-2025-10149 Arbitrary Operations via SCIM Endpoints in Multiple WSO2 Products Enables User Account Takeover 8h
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2024-4457 is "Remote Code Execution via JDBC User Store Configuration in Multiple WSO2 Products Allows Arbitrary Code Execution", rated Unknown. It affects Api Manager (WSO2); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.21% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.