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

> Attackers can access sensitive information via the config.php component in Joyplus CMS, potentially exposing configuration details.

- **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:** 18 Aug 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-v6v2-8q4w-pwmg

## What is CVE-2020-22124?

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

### Official description

A vulnerability in the \inc\config.php component of joyplus-cms v1.6 allows attackers to access sensitive information.

Weakness: CWE-552 (Files or Directories Accessible to External Parties)

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

It affects 1 product.


Products: Joyplus-Cms Project Joyplus-Cms.

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

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

## Is CVE-2020-22124 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-14389](https://insights.sbomify.com/CVE-2018-14389/): SQL injection in n/a (critical 9.8)
- [CVE-2018-14334](https://insights.sbomify.com/CVE-2018-14334/): File upload in n/a (critical 9.8)
- [CVE-2018-12039](https://insights.sbomify.com/CVE-2018-12039/): SQL injection in n/a (critical 9.8)
- [CVE-2018-8766](https://insights.sbomify.com/CVE-2018-8766/): File upload in n/a (critical 9.8)
- [CVE-2018-8717](https://insights.sbomify.com/CVE-2018-8717/): Cross-site request forgery in n/a (high 8.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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