CVE-2024-2323: Password Brute Force via Password History Validation in Multiple WSO2 Products Allows User Account Discovery
Noroxi assessment
Priority: Monitor (action score 19/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.22% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- 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 RemoteUserStoreManagerService does not sufficiently validate password change attempts when the password history validation feature is enabled. This oversight allows an attacker to repeatedly attempt password guesses for a user account without being adequately restricted. Exploiting this vulnerability enables an attacker to discover a user's password through brute force, leading to account impersonation. The success rate of such an attack is influenced by the complexity of the targeted user's password, with simpler passwords increasing the likelihood of compromise.
- Published
- Oct 20, 2026
- Updated
- Oct 20, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- CWE-307
Report tools
Action score
19
Monitor
Low priority for now.
- CVSS
- 19 / 40 · 4.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · WSO2
- 4.8
- NVD has not scored this yet; the score shown is the CNA’s.
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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.
—
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 Manager
- before 3.1.0unknown
- 3.1.0 and later · before 3.1.0.268affected
- 3.2.0 and later · before 3.2.0.354affected
WSO2 WSO2 Carbon User Manager Kernel
- 4.5.0 and later · before 4.5.0.4affected
- 4.5.3 and later · before 4.5.3.34affected
- 4.6.0 and later · before 4.6.0.137affected
- 4.6.1 and later · before 4.6.1.111affected
- 4.7.1 and later · before 4.7.1.51affected
- 4.9.0 and later · before 4.9.0.54affected
- 4.10.9 and later · before 4.10.9.20affected
WSO2 WSO2 Enterprise Integrator
- before 6.6.0unknown
- 6.6.0 and later · before 6.6.0.204affected
WSO2 WSO2 Identity Server
- before 5.10.0unknown
- 5.10.0 and later · before 5.10.0.286affected
- 5.11.0 and later · before 5.11.0.344affected
- 6.0.0 and later · before 6.0.0.188affected
- 6.1.0 and later · before 6.1.0.150affected
- 7.0.0 and later · before 7.0.0.35affected
WSO2 WSO2 Identity Server as Key Manager
- before 5.10.0unknown
- 5.10.0 and later · before 5.10.0.283affected
WSO2 WSO2 Open Banking AM
- before 2.0.0unknown
- 2.0.0 and later · before 2.0.0.315affected
WSO2 WSO2 Open Banking IAM
- before 2.0.0unknown
- 2.0.0 and later · before 2.0.0.335affected
Same product
wso2: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-4457Remote Code Execution via JDBC User Store Configuration in Multiple WSO2 Products Allows Arbitrary Code Execution36Monitor
- CVE-2024-7074Authenticated Arbitrary File Upload in Multiple WSO2 Products via SOAP Admin Service Leading to Remote Code Execution32Monitor
- CVE-2024-5139Cross-Site Scripting via Authentication Endpoint in Multiple WSO2 Products Enables UI Manipulation and Redirection24Monitor
Published before and after this one in the same product
- ← EarlierCVE-2025-12317Aug 6, 2026 · Improper Token Revocation via SOAP Services in Multiple WSO2 Products Allows Retained Access Privileges20Monitor
- ← EarlierCVE-2024-4412Oct 19, 2026 · Expression Language Injection via User Input in Multiple WSO2 Products Permits Arbitrary Operations10Monitor
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.
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 researchersFinders, 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.
No nightly-computed relations.
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.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-307 · Improper Restriction of Excessive Authentication AttemptsCVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Dictionary-based Password AttackCAPEC-16likelihood: Medium · High
- Password Brute ForcingCAPEC-49likelihood: Medium · High
- Use of Known Domain CredentialsCAPEC-560likelihood: High · High
- Password SprayingCAPEC-565likelihood: High · High
- Credential StuffingCAPEC-600likelihood: High · High
- Use of Known Kerberos CredentialsCAPEC-652likelihood: Medium · High
- Use of Known Operating System CredentialsCAPEC-653likelihood: High · High
Change log
- SSVC exploitation— → none
- Exploit maturity— → none
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.