# CVE-2020-23768: Information disclosure in n/a

> Attackers can obtain users' personally identifiable information from log files in the Alibaba payment interface of PHPPYUN.

- **Severity:** High 7.5 (`CVSS:3.1/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:** 21 May 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-fxj6-gm5w-8mwr

## What is CVE-2020-23768?

CVE-2020-23768 is a high-severity vulnerability in n/a, published on 21 May 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An information disclosure vulnerability was discovered in alipay_function.php in the log file of Alibaba payment interface on PHPPYUN prior to version 5.0.1. If exploited, this vulnerability will allow attackers to obtain users' personally identifiable information including e-mail address and telephone numbers.

## Which versions are affected by CVE-2020-23768?

It affects 1 product.


Products: Phpyun Phpyun.

## How do I fix CVE-2020-23768?

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

## Is CVE-2020-23768 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-18713](https://insights.sbomify.com/CVE-2018-18713/): Path traversal in n/a (high 7.5)
- [CVE-2018-18626](https://insights.sbomify.com/CVE-2018-18626/): Path traversal in n/a (high 7.5)
- [CVE-2010-4796](https://insights.sbomify.com/CVE-2010-4796/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-23768 and fix it if it is affected.

What it is: CVE-2020-23768 is a high-severity vulnerability in n/a, published on 21 May 2021. 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-2020-23768 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-2020-23768/ (Markdown: https://insights.sbomify.com/CVE-2020-23768/index.md)
```

## Sources

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

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