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

> Remote attackers can access sensitive internal files via unauthenticated requests with predictable URLs due to insecure direct object references.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-fvm3-gwpp-ccgq

## What is CVE-2020-15958?

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

### Official description

An issue was discovered in 1CRM System through 8.6.7. An insecure direct object reference to internally stored files allows a remote attacker to access various sensitive information via an unauthenticated request with a predictable URL.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

It affects 1 product.


Products: 1crm 1crm.

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

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

## Is CVE-2020-15958 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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