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

> Attackers can access all user accounts because passwords are stored without encryption in the Cleaning Business Software.

- **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:** 11 Sep 2023
- **Updated:** 26 Sep 2024
- **Also known as:** GHSA-rp33-8597-jc3x

## What is CVE-2023-36140?

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

### Official description

In PHPJabbers Cleaning Business Software 1.0, there is no encryption on user passwords allowing an attacker to gain access to all user accounts.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Phpjabbers Cleaning Business Software.

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

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

## Is CVE-2023-36140 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-36139](https://insights.sbomify.com/CVE-2023-36139/): Business logic in n/a (critical 9.8)
- [CVE-2023-51326](https://insights.sbomify.com/CVE-2023-51326/): Denial of service in n/a (medium 6.5)
- [CVE-2023-51327](https://insights.sbomify.com/CVE-2023-51327/): Denial of service in n/a (medium 6.5)
- [CVE-2023-51331](https://insights.sbomify.com/CVE-2023-51331/): Code injection in n/a (medium 6.5)
- [CVE-2023-36138](https://insights.sbomify.com/CVE-2023-36138/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-36140 is a critical vulnerability in n/a, published on 11 Sep 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-36140 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-36140/ (Markdown: https://insights.sbomify.com/CVE-2023-36140/index.md)
```

## Sources

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

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