# CVE-2019-11492: Information disclosure in n/a

> ProjectSend writes user passwords to server logs, allowing attackers with log access to steal credentials.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 26 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-j72j-hjpx-v29v

## What is CVE-2019-11492?

CVE-2019-11492 is a high-severity vulnerability in n/a, published on 26 Apr 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ProjectSend before r1070 writes user passwords to the server logs.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2019-11492?

It affects 1 product.


Products: Projectsend Projectsend.

## How do I fix CVE-2019-11492?

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

## Is CVE-2019-11492 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-11680](https://insights.sbomify.com/CVE-2024-11680/): ProjectSend Improper Authentication (critical 9.8, exploited in the wild)
- [CVE-2021-40887](https://insights.sbomify.com/CVE-2021-40887/): Path traversal in n/a (critical 9.8)
- [CVE-2016-10731](https://insights.sbomify.com/CVE-2016-10731/): SQL injection in n/a (critical 9.8)
- [CVE-2016-10732](https://insights.sbomify.com/CVE-2016-10732/): Auth bypass in n/a (critical 9.8)
- [CVE-2016-10733](https://insights.sbomify.com/CVE-2016-10733/): Path traversal in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-11492 and fix it if it is affected.

What it is: CVE-2019-11492 is a high-severity vulnerability in n/a, published on 26 Apr 2019. 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-2019-11492 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-2019-11492/ (Markdown: https://insights.sbomify.com/CVE-2019-11492/index.md)
```

## Sources

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

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