# CVE-2023-51321: Denial of service in n/a

> Attackers can cause denial of service by flooding a user's inbox via the unthrottled forgot password feature in PHPJabbers Night Club Booking Software.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Feb 2025
- **Updated:** 4 Nov 2025
- **Also known as:** GHSA-4rhc-2pqf-hqj3

## What is CVE-2023-51321?

CVE-2023-51321 is a medium-severity denial of service vulnerability in n/a, published on 20 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A lack of rate limiting in the 'Forgot Password' feature of PHPJabbers Night Club Booking Software v1.0 allows attackers to send an excessive amount of email for a legitimate user, leading to a possible Denial of Service (DoS) via a large amount of generated e-mail messages.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

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

It affects 1 product.


Products: Phpjabbers Night Club Booking Software.

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

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

## Is CVE-2023-51321 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-51320](https://insights.sbomify.com/CVE-2023-51320/): Code injection in n/a (medium 5.3)
- [CVE-2023-4114](https://insights.sbomify.com/CVE-2023-4114/): PHP Jabbers Night Club Booking Software index.php cross site scripting (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-51321 is a medium-severity denial of service vulnerability in n/a, published on 20 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-51321 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-51321/ (Markdown: https://insights.sbomify.com/CVE-2023-51321/index.md)
```

## Sources

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

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