# CVE-2019-16387: Missing authorization in n/a

> Low-privilege users may access administrative database functions via direct URL requests, though the vendor disputes the privilege level of the reporter.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Nov 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-cp7m-qccx-qc2g

## What is CVE-2019-16387?

CVE-2019-16387 is a high-severity missing authorization vulnerability in n/a, published on 26 Nov 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

PEGA Platform 8.3.0 is vulnerable to a direct prweb/sso/random_token/!STANDARD?pyActivity=Data-Admin-DB-Name.DBSchema_ListDatabases request while using a low-privilege account. (This can perform actions and retrieve data that only an administrator should have access to.) NOTE: The vendor states that this vulnerability was discovered using an administrator account and they are normal administrator functions. Therefore, the claim that the CVE was done with a low privilege account is incorrect

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere)

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

It affects 1 product.


Products: Pega Pega Platform.

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

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

## Is CVE-2019-16387 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-32090](https://insights.sbomify.com/CVE-2023-32090/): Hardcoded credentials in Pega Platform (critical 9.8)
- [CVE-2020-15390](https://insights.sbomify.com/CVE-2020-15390/): Missing authorization in n/a (critical 9.8)
- [CVE-2020-8774](https://insights.sbomify.com/CVE-2020-8774/): Cross-site scripting in n/a (high 8.8)
- [CVE-2025-2160](https://insights.sbomify.com/CVE-2025-2160/): Cross-site scripting in Pega Infinity (high 8.1)
- [CVE-2023-28094](https://insights.sbomify.com/CVE-2023-28094/): Hardcoded credentials in Pega Platform (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-16387 is a high-severity missing authorization vulnerability in n/a, published on 26 Nov 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-16387 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-16387/ (Markdown: https://insights.sbomify.com/CVE-2019-16387/index.md)
```

## Sources

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

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