# CVE-2023-33561: Weak cryptography in n/a

> Improper input validation in the booking calendar plugin allows insecure passwords, potentially enabling unauthorized access.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Aug 2023
- **Updated:** 21 Oct 2024
- **Also known as:** GHSA-x3xp-qp6c-rgqp

## What is CVE-2023-33561?

CVE-2023-33561 is a critical vulnerability in n/a, published on 1 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper input validation of password parameter in PHP Jabbers Time Slots Booking Calendar v 3.3 results in insecure passwords.

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

It affects 1 product.


Products: Phpjabbers Time Slots Booking Calendar.

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

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

## Is CVE-2023-33561 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-33561 exists.

## Other vulnerabilities in n/a

- [CVE-2023-33562](https://insights.sbomify.com/CVE-2023-33562/): Information disclosure in n/a (critical 9.8)
- [CVE-2023-48826](https://insights.sbomify.com/CVE-2023-48826/): Other in n/a (high 8.8)
- [CVE-2023-33563](https://insights.sbomify.com/CVE-2023-33563/): Auth bypass in n/a (high 8.8)
- [CVE-2023-48833](https://insights.sbomify.com/CVE-2023-48833/): Denial of service in n/a (high 7.5)
- [CVE-2023-33560](https://insights.sbomify.com/CVE-2023-33560/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-33561 is a critical vulnerability in n/a, published on 1 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-33561 exists.

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-33561/ (Markdown: https://insights.sbomify.com/CVE-2023-33561/index.md)
```

## Sources

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

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