# CVE-2019-16403: Authorization Bypass Through User-Controlled Key in Bagisto

> Attackers can manipulate other customers' data such as addresses and orders due to missing authorization checks in Bagisto.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Sep 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-pwrf-q7h8-jjr7

## What is CVE-2019-16403?

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

### Official description

In Webkul Bagisto before 0.1.5, the functionalities for customers to change their own values (such as address, review, orders, etc.) can also be manipulated by other customers.

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

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `bagisto/bagisto` | Packagist | All versions | 0.1.5 |
| `bagisto/bagisto` | Packagist | All versions | 0.1.5 |

Products: Webkul Bagisto.

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

Upgrade bagisto/bagisto to 0.1.5 or later.

## Is CVE-2019-16403 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-21448](https://insights.sbomify.com/CVE-2026-21448/): Bagisto has Normal & Blind SSTI from low-privilege user when ordering product (high 8.9)
- [CVE-2026-21446](https://insights.sbomify.com/CVE-2026-21446/): Bagisto Missing Authentication on Installer API Endpoints (high 8.8)
- [CVE-2023-36237](https://insights.sbomify.com/CVE-2023-36237/): Bagisto Cross-Site Request Forgery vulnerability (high 8.8)
- [CVE-2023-33570](https://insights.sbomify.com/CVE-2023-33570/): Code injection in n/a (high 8.8)
- [CVE-2019-14933](https://insights.sbomify.com/CVE-2019-14933/): Bagisto CSRF Vulnerability (high 8.8)

## Fix prompt for AI coding agents

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

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

Affected packages and fixed versions:
- bagisto/bagisto (Packagist): affected all versions; fixed in 0.1.5
- bagisto/bagisto (Packagist): affected all versions; fixed in 0.1.5

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

## Sources

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

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