# CVE-2023-34732: Other in n/a

> Attackers can brute force user passwords via the change password function due to missing rate limiting, potentially leading to account takeover.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 May 2025
- **Updated:** 13 May 2025
- **Also known as:** GHSA-2xwv-25cq-66xr

## What is CVE-2023-34732?

CVE-2023-34732 is a medium-severity vulnerability in n/a, published on 12 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue in the userId parameter in the change password function of Flytxt NEON-dX v0.0.1-SNAPSHOT-6.9-qa-2-9-g5502a0c allows attackers to execute brute force attacks to discover user passwords.

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

## Which versions are affected by CVE-2023-34732?

It affects 1 product.


Products: Flytxt Neon-Dx.

## How do I fix CVE-2023-34732?

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

## Is CVE-2023-34732 being exploited?

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

Public exploit code:

- https://github.com/saykino/CVE-2023-34732 (github_poc): https://github.com/saykino/CVE-2023-34732

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-34732 and fix it if it is affected.

What it is: CVE-2023-34732 is a medium-severity vulnerability in n/a, published on 12 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-34732 in the wild and no public exploit code.

Affected product: n/a. 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-2023-34732/ (Markdown: https://insights.sbomify.com/CVE-2023-34732/index.md)
```

## Sources

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

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