# CVE-2019-16669: Pagekit User enumeration

> Attackers can enumerate valid user accounts via inconsistent responses in the password reset feature, facilitating targeted attacks.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 Sep 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jh2j-7248-9p3c

## What is CVE-2019-16669?

CVE-2019-16669 is a medium-severity vulnerability in n/a, published on 21 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Reset Password feature in Pagekit 1.0.17 gives a different response depending on whether the e-mail address of a valid user account is entered, which might make it easier for attackers to enumerate accounts.

Weakness: CWE-203 (Observable Discrepancy)

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

2 open source packages ship an affected version, including pagekit/pagekit. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pagekit/pagekit` | Packagist | All versions | None |
| `pagekit/pagekit` | Packagist | All versions | None |

Products: Pagekit Pagekit.

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

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

## Is CVE-2019-16669 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-67164](https://insights.sbomify.com/CVE-2025-67164/): Pagekit CMS is vulnerable to OS Command Injection via Storage component (critical 9.9)
- [CVE-2025-67165](https://insights.sbomify.com/CVE-2025-67165/): Pagekit CMS has an Insecure Direct Object Reference (IDOR) in its User Role component (critical 9.8)
- [CVE-2022-38916](https://insights.sbomify.com/CVE-2022-38916/): Pagekit vulnerable to Unrestricted Upload of File with Dangerous Type (critical 9.8)
- [CVE-2021-44135](https://insights.sbomify.com/CVE-2021-44135/): SQL injection in pagekit/pagekit (critical 9.8)
- [CVE-2019-19013](https://insights.sbomify.com/CVE-2019-19013/): Pagekit File Upload vulnerability (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-16669 is a medium-severity vulnerability in n/a, published on 21 Sep 2019. 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-16669 in the wild and no public exploit code.

Affected packages and fixed versions:
- pagekit/pagekit (Packagist): affected all versions; no fix listed
- pagekit/pagekit (Packagist): affected all versions; no fix listed

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-16669/ (Markdown: https://insights.sbomify.com/CVE-2019-16669/index.md)
```

## Sources

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

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