# CVE-2019-18608: Cezerin Unauthorized Acces

> Attackers can manipulate order details like payment status by injecting attributes during checkout, affecting e-commerce integrity.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 29 Oct 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-6pq6-crw9-522h

## What is CVE-2019-18608?

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

### Official description

Cezerin v0.33.0 allows unauthorized order-information modification because certain internal attributes can be overwritten via a conflicting name when processing order requests. Hence, a malicious customer can manipulate an order (e.g., its payment status or shipping fee) by adding additional attributes to user-input during the PUT /ajax/cart operation for a checkout, because of getValidDocumentForUpdate in api/server/services/orders/orders.js.

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `cezerin` | npm | All versions to 0.33.0 | None |
| `cezerin` | npm | All versions to 0.33.0 | None |

Products: Cezerin Cezerin.

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

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

## Is CVE-2019-18608 being exploited?

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

## Fix prompt for AI coding agents

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

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

Affected packages and fixed versions:
- cezerin (npm): affected all versions up to 0.33.0; no fix listed
- cezerin (npm): affected all versions up to 0.33.0; 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-18608/ (Markdown: https://insights.sbomify.com/CVE-2019-18608/index.md)
```

## Sources

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

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