# CVE-2024-2323: Password Brute Force via Password History Validation in Multiple WSO2 Products Allows User Account Discovery


- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-jqjg-fvqg-f5xq

## What is CVE-2024-2323?

CVE-2024-2323 is a medium-severity vulnerability in WSO2 API Manager, published on 20 Oct 2026. 

### Official description

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.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

## Which versions are affected by CVE-2024-2323?


## How do I fix CVE-2024-2323?

No fix has been published for CVE-2024-2323 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-2323 being exploited?

There is no known exploitation of CVE-2024-2323 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-2323 and fix it if it is affected.

What it is: CVE-2024-2323 is a medium-severity vulnerability in WSO2 API Manager, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2024-2323 in the wild and no public exploit code.

Affected product: WSO2 API Manager. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-2323/ (Markdown: https://insights.sbomify.com/CVE-2024-2323/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-2323
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-2323
- OSV: https://osv.dev/vulnerability/CVE-2024-2323

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-2323/
Summaries are generated and may contain mistakes; the official description above is the record.