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

> Unauthorized users can access admin-only pages on ZyXEL P-1302-T10D routers due to improper access control enforcement.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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:** 12 Nov 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-v5v2-65jc-4g4f

## What is CVE-2019-15815?

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

### Official description

ZyXEL P-1302-T10D v3 devices with firmware version 2.00(ABBX.3) and earlier do not properly enforce access control and could allow an unauthorized user to access certain pages that require admin privileges.

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

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

It affects 1 product.


Products: Zyxel 2.00\(abbx.3\).

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

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

## Is CVE-2019-15815 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-15815 is a medium-severity missing authorization vulnerability in n/a, published on 12 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-15815 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-15815/ (Markdown: https://insights.sbomify.com/CVE-2019-15815/index.md)
```

## Sources

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

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