# CVE-2001-1357: Other in n/a

> Multiple vulnerabilities in phpMyChat allow user spoofing or variable manipulation, potentially compromising chat integrity.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** 11 Jun 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-3x49-p9xf-cg52

## What is CVE-2001-1357?

CVE-2001-1357 is a high-severity vulnerability in n/a, published on 11 Jun 2002. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple vulnerabilities in phpMyChat before 0.14.5 exist in (1) input.php3, (2) handle_inputH.php3, or (3) index.lib.php3 with unknown consequences, possibly related to user spoofing or improperly initialized variables.

## Which versions are affected by CVE-2001-1357?

It affects 1 product.


Products: Phpheaven Phpmychat.

## How do I fix CVE-2001-1357?

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

## Is CVE-2001-1357 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-5088](https://insights.sbomify.com/CVE-2006-5088/): Code injection in n/a (high 7.5)
- [CVE-2001-1358](https://insights.sbomify.com/CVE-2001-1358/): Path traversal in n/a (high 7.2)
- [CVE-2006-1669](https://insights.sbomify.com/CVE-2006-1669/): SQL injection in n/a (medium 6.4)
- [CVE-2006-5898](https://insights.sbomify.com/CVE-2006-5898/): Path traversal in n/a (medium 5.0)
- [CVE-2008-1504](https://insights.sbomify.com/CVE-2008-1504/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2001-1357 and fix it if it is affected.

What it is: CVE-2001-1357 is a high-severity vulnerability in n/a, published on 11 Jun 2002. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2001-1357 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-2001-1357/ (Markdown: https://insights.sbomify.com/CVE-2001-1357/index.md)
```

## Sources

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

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