CVE-2026-4249 Vulnerability Analysis & Exploit Details

CVE-2026-4249
Vulnerability Scoring

8.6
/10
Severe Risk

Cybersecurity professionals consider CVE-2026-4249 an immediate threat requiring urgent mitigation.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Changed
    Successful exploitation can impact components beyond the vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-4249 Details

Status: Analyzed

Last updated: 🕐 09 Jul 2026, 13:04 UTC
Originally published on: 🕚 06 Jul 2026, 11:16 UTC

Time between publication and last update: 3 days

CVSS Release: version 3

CVSS3 Source

ed10eef1-636d-4fbe-9993-6890dfa878f8

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H

CVE-2026-4249 Vulnerability Summary

CVE-2026-4249: The throttling event handling mechanism in multiple WSO2 products accepts user-supplied JSON payloads without sufficient validation of their structure and content. This allows an unauthenticated remote attacker to inject malicious JSON data that can lead to a persistent denial of service condition. Successful exploitation of this vulnerability can disrupt the API Gateway, preventing legitimate API traffic from being processed and impacting complete service availability. The denial of service is persistent, requiring manual intervention to restore normal operations.

Assessing the Risk of CVE-2026-4249

Access Complexity Graph

The exploitability of CVE-2026-4249 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-4249

With low attack complexity and no required privileges, CVE-2026-4249 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-4249, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-4249, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2026-4249 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2026-4249 poses no threat to data integrity.
  • Availability: High
    CVE-2026-4249 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2026-4249 References

External References

CWE Common Weakness Enumeration

CWE-707

CAPEC Common Attack Pattern Enumeration and Classification

  • XML Injection CAPEC-250 An attacker utilizes crafted XML user-controllable input to probe, attack, and inject data into the XML database, using techniques similar to SQL injection. The user-controllable input can allow for unauthorized viewing of data, bypassing authentication or the front-end application for direct XML database access, and possibly altering database information.
  • Inter-component Protocol Manipulation CAPEC-276 Inter-component protocols are used to communicate between different software and hardware modules within a single computer. Common examples are: interrupt signals and data pipes. Subverting the protocol can allow an adversary to impersonate others, discover sensitive information, control the outcome of a session, or perform other attacks. This type of attack targets invalid assumptions that may be inherent in implementers of the protocol, incorrect implementations of the protocol, or vulnerabilities in the protocol itself.
  • Data Interchange Protocol Manipulation CAPEC-277 Data Interchange Protocols are used to transmit structured data between entities. These protocols are often specific to a particular domain (B2B: purchase orders, invoices, transport logistics and waybills, medical records). They are often, but not always, XML-based. Subverting the protocol can allow an adversary to impersonate others, discover sensitive information, control the outcome of a session, or perform other attacks. This type of attack targets invalid assumptions that may be inherent in implementers of the protocol, incorrect implementations of the protocol, or vulnerabilities in the protocol itself.
  • Web Services Protocol Manipulation CAPEC-278 An adversary manipulates a web service related protocol to cause a web application or service to react differently than intended. This can either be performed through the manipulation of call parameters to include unexpected values, or by changing the called function to one that should normally be restricted or limited. By leveraging this pattern of attack, the adversary is able to gain access to data or resources normally restricted, or to cause the application or service to crash.
  • SOAP Manipulation CAPEC-279 Simple Object Access Protocol (SOAP) is used as a communication protocol between a client and server to invoke web services on the server. It is an XML-based protocol, and therefore suffers from many of the same shortcomings as other XML-based protocols. Adversaries can make use of these shortcomings and manipulate the content of SOAP paramters, leading to undesirable behavior on the server and allowing the adversary to carry out a number of further attacks.
  • Using Leading 'Ghost' Character Sequences to Bypass Input Filters CAPEC-3 Some APIs will strip certain leading characters from a string of parameters. An adversary can intentionally introduce leading "ghost" characters (extra characters that don't affect the validity of the request at the API layer) that enable the input to pass the filters and therefore process the adversary's input. This occurs when the targeted API will accept input data in several syntactic forms and interpret it in the equivalent semantic way, while the filter does not take into account the full spectrum of the syntactic forms acceptable to the targeted API.
  • Exploiting Multiple Input Interpretation Layers CAPEC-43 An attacker supplies the target software with input data that contains sequences of special characters designed to bypass input validation logic. This exploit relies on the target making multiples passes over the input data and processing a "layer" of special characters with each pass. In this manner, the attacker can disguise input that would otherwise be rejected as invalid by concealing it with layers of special/escape characters that are stripped off by subsequent processing steps. The goal is to first discover cases where the input validation layer executes before one or more parsing layers. That is, user input may go through the following logic in an application: <parser1> --> <input validator> --> <parser2>. In such cases, the attacker will need to provide input that will pass through the input validator, but after passing through parser2, will be converted into something that the input validator was supposed to stop.
  • Generic Cross-Browser Cross-Domain Theft CAPEC-468 An attacker makes use of Cascading Style Sheets (CSS) injection to steal data cross domain from the victim's browser. The attack works by abusing the standards relating to loading of CSS: 1. Send cookies on any load of CSS (including cross-domain) 2. When parsing returned CSS ignore all data that does not make sense before a valid CSS descriptor is found by the CSS parser.
  • Embedding NULL Bytes CAPEC-52 An adversary embeds one or more null bytes in input to the target software. This attack relies on the usage of a null-valued byte as a string terminator in many environments. The goal is for certain components of the target software to stop processing the input when it encounters the null byte(s).
  • Postfix, Null Terminate, and Backslash CAPEC-53 If a string is passed through a filter of some kind, then a terminal NULL may not be valid. Using alternate representation of NULL allows an adversary to embed the NULL mid-string while postfixing the proper data so that the filter is avoided. One example is a filter that looks for a trailing slash character. If a string insertion is possible, but the slash must exist, an alternate encoding of NULL in mid-string may be used.
  • Using Slashes and URL Encoding Combined to Bypass Validation Logic CAPEC-64 This attack targets the encoding of the URL combined with the encoding of the slash characters. An attacker can take advantage of the multiple ways of encoding a URL and abuse the interpretation of the URL. A URL may contain special character that need special syntax handling in order to be interpreted. Special characters are represented using a percentage character followed by two digits representing the octet code of the original character (%HEX-CODE). For instance US-ASCII space character would be represented with %20. This is often referred as escaped ending or percent-encoding. Since the server decodes the URL from the requests, it may restrict the access to some URL paths by validating and filtering out the URL requests it received. An attacker will try to craft an URL with a sequence of special characters which once interpreted by the server will be equivalent to a forbidden URL. It can be difficult to protect against this attack since the URL can contain other format of encoding such as UTF-8 encoding, Unicode-encoding, etc.
  • Blind SQL Injection CAPEC-7 Blind SQL Injection results from an insufficient mitigation for SQL Injection. Although suppressing database error messages are considered best practice, the suppression alone is not sufficient to prevent SQL Injection. Blind SQL Injection is a form of SQL Injection that overcomes the lack of error messages. Without the error messages that facilitate SQL Injection, the adversary constructs input strings that probe the target through simple Boolean SQL expressions. The adversary can determine if the syntax and structure of the injection was successful based on whether the query was executed or not. Applied iteratively, the adversary determines how and where the target is vulnerable to SQL Injection.
  • Using Escaped Slashes in Alternate Encoding CAPEC-78 This attack targets the use of the backslash in alternate encoding. An adversary can provide a backslash as a leading character and causes a parser to believe that the next character is special. This is called an escape. By using that trick, the adversary tries to exploit alternate ways to encode the same character which leads to filter problems and opens avenues to attack.
  • Using Slashes in Alternate Encoding CAPEC-79 This attack targets the encoding of the Slash characters. An adversary would try to exploit common filtering problems related to the use of the slashes characters to gain access to resources on the target host. Directory-driven systems, such as file systems and databases, typically use the slash character to indicate traversal between directories or other container components. For murky historical reasons, PCs (and, as a result, Microsoft OSs) choose to use a backslash, whereas the UNIX world typically makes use of the forward slash. The schizophrenic result is that many MS-based systems are required to understand both forms of the slash. This gives the adversary many opportunities to discover and abuse a number of common filtering problems. The goal of this pattern is to discover server software that only applies filters to one version, but not the other.
  • XPath Injection CAPEC-83 An attacker can craft special user-controllable input consisting of XPath expressions to inject the XML database and bypass authentication or glean information that they normally would not be able to. XPath Injection enables an attacker to talk directly to the XML database, thus bypassing the application completely. XPath Injection results from the failure of an application to properly sanitize input used as part of dynamic XPath expressions used to query an XML database.
  • XQuery Injection CAPEC-84 This attack utilizes XQuery to probe and attack server systems; in a similar manner that SQL Injection allows an attacker to exploit SQL calls to RDBMS, XQuery Injection uses improperly validated data that is passed to XQuery commands to traverse and execute commands that the XQuery routines have access to. XQuery injection can be used to enumerate elements on the victim's environment, inject commands to the local host, or execute queries to remote files and data sources.

Vulnerable Configurations

  • cpe:2.3:a:wso2:api_control_plane:4.5.0:-:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_control_plane:4.5.0:-:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_control_plane:4.5.0.29:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_control_plane:4.5.0.29:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.0.0.168:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.0.0.168:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.0.0.217:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.0.0.217:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.0.0.280:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.0.0.280:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.0.0.293:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.0.0.293:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.0.0.305:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.0.0.305:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.0.0.310:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.0.0.310:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.0.0.318:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.0.0.318:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.0.0.319:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.0.0.319:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.0.0.355:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.0.0.355:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.0.0.368:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.0.0.368:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.0.0.370:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.0.0.370:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.0.0.373:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.0.0.373:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.0.0.375:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.0.0.375:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.0.0.381:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.0.0.381:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.1.0:-:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.1.0:-:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.1.0:m1:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.1.0:m1:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.1.0:m2:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.1.0:m2:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.1.0:m3:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.1.0:m3:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.1.0:m4:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.1.0:m4:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.1.0:rc:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.1.0:rc:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.1.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.1.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.1.0:rc3:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.1.0:rc3:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.1.0.136:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.1.0.136:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.1.0.152:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.1.0.152:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.1.0.166:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.1.0.166:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.1.0.171:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.1.0.171:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.1.0.187:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.1.0.187:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.1.0.200:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.1.0.200:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.1.0.206:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.1.0.206:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.1.0.215:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.1.0.215:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.1.0.216:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.1.0.216:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.1.0.218:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.1.0.218:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.1.0.219:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.1.0.219:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.1.0.228:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.1.0.228:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.1.0.231:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.1.0.231:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.1.0.233:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.1.0.233:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.1.0.236:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.1.0.236:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.1.0.238:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.1.0.238:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.1.0.242:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.1.0.242:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.1.0.244:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.1.0.244:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.2.0:-:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.2.0:-:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.2.0:m1:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.2.0:m1:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.2.0.80:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.2.0.80:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.2.0:rc:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.2.0:rc:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.2.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.2.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.2.0.100:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.2.0.100:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.2.0.108:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.2.0.108:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.2.0.127:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.2.0.127:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.2.0.138:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.2.0.138:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.2.0.144:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.2.0.144:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.2.0.150:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.2.0.150:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.2.0.153:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.2.0.153:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.2.0.156:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.2.0.156:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.2.0.157:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.2.0.157:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.2.0.164:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.2.0.164:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.2.0.169:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.2.0.169:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.2.0.171:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.2.0.171:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.2.0.173:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.2.0.173:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.2.0.176:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.2.0.176:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.2.0.178:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.2.0.178:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.2.0.179:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.2.0.179:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.2.0.182:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.2.0.182:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.2.0.184:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.2.0.184:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.3.0:-:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.3.0:-:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.3.0.16:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.3.0.16:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.3.0.39:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.3.0.39:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.3.0.51:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.3.0.51:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.3.0.55:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.3.0.55:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.3.0.57:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.3.0.57:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.3.0.65:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.3.0.65:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.3.0.66:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.3.0.66:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.3.0.67:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.3.0.67:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.3.0.70:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.3.0.70:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.3.0.74:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.3.0.74:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.3.0.81:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.3.0.81:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.3.0.83:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.3.0.83:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.3.0.85:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.3.0.85:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.3.0.88:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.3.0.88:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.3.0.90:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.3.0.90:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.3.0.91:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.3.0.91:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.3.0.93:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.3.0.93:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.3.0.95:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.3.0.95:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.4.0:-:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.4.0:-:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.4.0.28:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.4.0.28:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.4.0.29:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.4.0.29:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.4.0.30:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.4.0.30:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.4.0.33:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.4.0.33:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.4.0.38:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.4.0.38:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.4.0.45:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.4.0.45:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.4.0.47:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.4.0.47:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.4.0.49:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.4.0.49:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.4.0.52:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.4.0.52:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.4.0.54:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.4.0.54:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.4.0.55:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.4.0.55:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.4.0.57:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.4.0.57:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.4.0.59:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.4.0.59:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.5.0:-:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.5.0:-:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.5.0.9:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.5.0.9:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.5.0.11:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.5.0.11:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.5.0.12:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.5.0.12:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.5.0.14:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.5.0.14:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.5.0.17:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.5.0.17:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.5.0.20:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.5.0.20:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.5.0.28:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.5.0.28:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.5.0.30:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.5.0.30:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.5.0.32:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.5.0.32:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.5.0.35:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.5.0.35:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.5.0.37:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.5.0.37:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.5.0.38:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.5.0.38:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.5.0.41:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.5.0.41:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.5.0.44:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.5.0.44:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.6.0:-:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.6.0:-:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.6.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.6.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.6.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.6.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.6.0.3:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.6.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.6.0.6:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.6.0.6:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.6.0.8:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.6.0.8:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:api_manager:4.6.0:m1:*:*:*:*:*:*
    cpe:2.3:a:wso2:api_manager:4.6.0:m1:*:*:*:*:*:*
  • cpe:2.3:a:wso2:traffic_manager:4.5.0:-:*:*:*:*:*:*
    cpe:2.3:a:wso2:traffic_manager:4.5.0:-:*:*:*:*:*:*
  • cpe:2.3:a:wso2:traffic_manager:4.5.0.27:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:traffic_manager:4.5.0.27:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:traffic_manager:4.6.0:-:*:*:*:*:*:*
    cpe:2.3:a:wso2:traffic_manager:4.6.0:-:*:*:*:*:*:*
  • cpe:2.3:a:wso2:universal_gateway:4.5.0:-:*:*:*:*:*:*
    cpe:2.3:a:wso2:universal_gateway:4.5.0:-:*:*:*:*:*:*
  • cpe:2.3:a:wso2:universal_gateway:4.5.0.27:*:*:*:*:*:*:*
    cpe:2.3:a:wso2:universal_gateway:4.5.0.27:*:*:*:*:*:*:*
  • cpe:2.3:a:wso2:universal_gateway:4.6.0:-:*:*:*:*:*:*
    cpe:2.3:a:wso2:universal_gateway:4.6.0:-:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-4249: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-85200 – The GEO my WP plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 4.5.5.3 via the gmw_posts_locator_aj...
  • CVE-2026-85198 – The MPG – Multiple Page Generator, Bulk Landing Pages & Programmatic SEO plugin for WordPress is vulnerable to generic SQL Injection via URL Path i...
  • CVE-2026-78175 – The Tutor LMS – eLearning and online course solution plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and includin...
  • CVE-2026-78159 – The The Events Calendar plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 6.17.3 via the parse_arra...
  • CVE-2026-78006 – The The Events Calendar plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 6.17.4 via the is_safe_wi...