VulnerabilityPublished 6 Aug 2026

CVE-2024-6832: WSO2 Enterprise Integrator · Protection Mechanism Failure

Affects WSO2 Enterprise IntegratorSource CVE Database V5

Compare

Not known to be exploited · CVSS 5.9 Medium : upgrade to 6.6.0.229 when convenient.

Data as of 5 Nov 2026, 23:23 UTC

CVSS 3.1 base score

5.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 6.6.0.229, 4.6.0.5, 4.6.0.4 +34

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

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-fr4m-mcg5-8cpc

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
WSO2WSO2 Enterprise Integrator	Affected >=6.6.0 <6.6.0.229	Fixed in 6.6.0.229
WSO2WSO2 API Control Plane	Affected >=4.6.0 <4.6.0.5	Fixed in 4.6.0.5
WSO2WSO2 API Control Plane	Affected >=4.6.0 <4.6.0.4	Fixed in 4.6.0.4
WSO2WSO2 API Control Plane	Affected >=4.5.0 <4.5.0.40	Fixed in 4.5.0.40
WSO2WSO2 Traffic Manager	Affected >=4.6.0 <4.6.0.5	Fixed in 4.6.0.5
WSO2WSO2 Traffic Manager	Affected >=4.6.0 <4.6.0.4	Fixed in 4.6.0.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, organizations should monitor authentication attempts and consider additional protective controls such as multi-factor authentication to mitigate brute force risks.

Description

CVE-2024-6832 is a vulnerability in WSO2 Enterprise Integrator version 6.6.0 where the account locking mechanism fails to activate if secondary user stores are inaccessible. This inconsistency allows attackers to repeatedly attempt invalid authentications without triggering account lockout for users in accessible stores, exposing them to brute force attacks. The vulnerability has a medium severity with a CVSS score of 5.9.

Impact

Users in accessible user stores remain vulnerable to brute force attacks since the account lockout mechanism does not trigger when secondary user stores are unreachable. This could lead to unauthorized access if an attacker successfully guesses credentials. The confidentiality impact is high, while integrity and availability impacts are not affected.

Summary

The vulnerability arises because the account locking mechanism in WSO2 Enterprise Integrator 6.6.0 does not maintain a consistent state when secondary user stores cannot be reached. As a result, the lockout mechanism is bypassed for users in accessible stores, enabling attackers to perform repeated invalid login attempts without triggering account lockout. This is classified under CWE-693 (Protection Mechanism Failure).

CWE-693Protection Mechanism Failure (opens in a new tab)
Pillar weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
Attack patterns
Accessing Functionality Not Properly Constrained by ACLs (opens in a new tab)
Cross Site Tracing (opens in a new tab)
Directory Indexing (opens in a new tab)
Using Malicious Files (opens in a new tab)
Encryption Brute Forcing (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-3352/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 13 Aug 2026, 17:32 UTC

WeaknessesCWE-693

Technical details

References

Community reviews

Related threats