Skip to content
Noroxi
NVD / CVE Program· CNA WSO2

CVE-2024-6832: Account Lockout Failure via Secondary User Store Inaccessibility in Multiple WSO2 Products Allows Brute Force Attacks

Noroxi assessment

Priority: Monitor (action score 30/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.41% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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 triggering the lockout mechanism for users within active stores. When the account locking mechanism is bypassed due to the inaccessibility of secondary user stores, users in accessible user stores are left vulnerable to brute force attacks. A malicious actor can exploit this by attempting numerous invalid password combinations against a user account without the expected account lockout consequence.

HighCVSS 7.5 · v3.1—No exploit No fix recorded
Published
Aug 6, 2026
Updated
Oct 27, 2026
EPSS
0.4% · 35th percentile

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.5
CNA · WSO2
5.9
1.6 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-6832

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for wso2 records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
wso2api control plane
wso2api manager
wso2identity server
wso2identity server as key manager
wso2open banking am
wso2open banking iam
wso2traffic manager
wso2universal gateway

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • wso2 api control plane4.5.0
  • wso2 api control plane4.6.0
  • wso2 api manager3.1.0
  • wso2 api manager3.2.0
  • wso2 api manager3.2.1
  • wso2 api manager4.1.0
  • wso2 api manager4.2.0
  • wso2 api manager4.3.0
  • wso2 api manager4.4.0
  • wso2 api manager4.5.0
  • wso2 api manager4.6.0
  • wso2 identity server5.10.0
  • wso2 identity server5.11.0
  • wso2 identity server6.0.0
  • wso2 identity server6.1.0
  • wso2 identity server7.0.0
  • wso2 identity server as key manager5.10.0
  • wso2 open banking am2.0.0
  • wso2 open banking iam2.0.0
  • wso2 traffic manager4.5.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (WSO2). Independent of NVD's CPE analysis and usually ahead of it.

  • WSO2 WSO2 API Control Plane

    • before 4.5.0unknown
    • 4.5.0 and later · before 4.5.0.40affected
    • 4.6.0 and later · before 4.6.0.4affected
    • 4.6.0 and later · before 4.6.0.5affected

  • WSO2 WSO2 API Manager

    • before 3.1.0unknown
    • 3.1.0 and later · before 3.1.0.296affected
    • 3.2.0 and later · before 3.2.0.386affected
    • 3.2.0 and later · before 3.2.0.455affected
    • 3.2.1 and later · before 3.2.1.74affected
    • 4.1.0 and later · before 4.1.0.238affected
    • 4.2.0 and later · before 4.2.0.179affected
    • 4.3.0 and later · before 4.3.0.91affected
    • 4.4.0 and later · before 4.4.0.55affected
    • 4.5.0 and later · before 4.5.0.39affected

  • WSO2 WSO2 Carbon User Manager Kernel

    • 4.5.0 and later · before 4.5.0.7affected
    • 4.5.3 and later · before 4.5.3.53affected
    • 4.6.0 and later · before 4.6.0.196affected
    • 4.6.1 and later · before 4.6.1.163affected
    • 4.6.1 and later · before 4.6.1.164affected
    • 4.6.3 and later · before 4.6.3.44affected
    • 4.6.4 and later · before 4.6.4.25affected
    • 4.7.1 and later · before 4.7.1.77affected
    • 4.7.1 and later · before 4.7.1.78affected
    • 4.8.1 and later · before 4.8.1.46affected

  • WSO2 WSO2 Enterprise Integrator

    • before 6.6.0unknown
    • 6.6.0 and later · before 6.6.0.229affected

  • WSO2 WSO2 Identity Server

    • before 5.10.0unknown
    • 5.10.0 and later · before 5.10.0.320affected
    • 5.11.0 and later · before 5.11.0.427affected
    • 6.0.0 and later · before 6.0.0.254affected
    • 6.1.0 and later · before 6.1.0.195affected
    • 7.0.0 and later · before 7.0.0.82affected

  • WSO2 WSO2 Identity Server as Key Manager

    • before 5.10.0unknown
    • 5.10.0 and later · before 5.10.0.314affected

  • WSO2 WSO2 Open Banking AM

    • before 2.0.0unknown
    • 2.0.0 and later · before 2.0.0.345affected

  • WSO2 WSO2 Open Banking IAM

    • before 2.0.0unknown
    • 2.0.0 and later · before 2.0.0.366affected

  • WSO2 WSO2 Traffic Manager

    • before 4.5.0unknown
    • 4.5.0 and later · before 4.5.0.38affected
    • 4.6.0 and later · before 4.6.0.4affected
    • 4.6.0 and later · before 4.6.0.5affected

  • WSO2 WSO2 Universal Gateway

    • before 4.5.0unknown
    • 4.5.0 and later · before 4.5.0.38affected
    • 4.6.0 and later · before 4.6.0.4affected
    • 4.6.0 and later · before 4.6.0.5affected

Same product

wso2: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-5430Authentication Bypass via JWT Algorithm Mismatch in Multiple WSO2 Products Allows Account TakeoverKEV
    77This week
  • CVE-2026-1728Privilege Escalation via System REST APIs in Multiple WSO2 Products Permits Admin Account Takeover
    39Monitor
  • CVE-2025-9312Improper Certificate-Based Authentication Enforcement in Multiple WSO2 Products
    39Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2026-0637Aug 6, 2026 · Sensitive Information Disclosure via Event Publisher Logging in Multiple WSO2 Products
    17Monitor
  • ← EarlierCVE-2024-10302Aug 6, 2026 · Improper Input Validation via Signup Process in Multiple WSO2 Products Enables Content Manipulation and Data Exposure
    23Monitor
  • Later →CVE-2024-8995Aug 6, 2026 · Authorization Code issued for Deleted User reuse in Multiple WSO2 Products Allows Unauthorized Access
    19Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2025-150390 days apartAccount Takeover via Conditional Authentication Script Logic in Multiple WSO2 Products
    37Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

Weakness class (CWE)

CWE-693 · Protection Mechanism Failure

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records