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

> Attackers can access sensitive report data without authentication because generated files are stored publicly instead of privately.

- **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 Mar 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-hx8g-7xcj-q9fh

## What is CVE-2019-20529?

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

### Official description

In core/doctype/prepared_report/prepared_report.py in Frappe 11 and 12, data files generated with Prepared Report were being stored as public files (no authentication is required to access; having a link is sufficient) instead of private files.

Weakness: CWE-552 (Files or Directories Accessible to External Parties), CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 1 product.


Products: Frappe Frappe.

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

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

## Is CVE-2019-20529 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-14965](https://insights.sbomify.com/CVE-2019-14965/): Code injection in n/a (critical 9.8)
- [CVE-2026-35614](https://insights.sbomify.com/CVE-2026-35614/): Frappe has a SQL injection in bulk_update (critical 9.3)
- [CVE-2026-31877](https://insights.sbomify.com/CVE-2026-31877/): Frappe SQL Injection due to improper field sanitization (critical 9.3)
- [CVE-2025-68929](https://insights.sbomify.com/CVE-2025-68929/): Frappe may be vulnerable remote code execution due to server-side template injection (critical 9.1)
- [CVE-2019-14966](https://insights.sbomify.com/CVE-2019-14966/): SQL injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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