# CVE-2020-9009: Missing authorization in n/a

> Remote attackers can modify database records in the ShipStation CS-Cart plugin due to missing authorization checks on the shipnotify endpoint.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/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:** 11 Apr 2023
- **Updated:** 11 Feb 2025
- **Also known as:** GHSA-rgw9-2qv4-ghxq

## What is CVE-2020-9009?

CVE-2020-9009 is a low-severity missing authorization vulnerability in n/a, published on 11 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The ShipStation.com plugin 1.1 and earlier for CS-Cart allows remote attackers to insert arbitrary information into the database (via action=shipnotify) because access to this endpoint is completely unchecked. The attacker must guess an order number.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2020-9009?

It affects 1 product.


Products: Shipstation Shipstation.

## How do I fix CVE-2020-9009?

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

## Is CVE-2020-9009 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-9009 exists.

## Other vulnerabilities in n/a

- [CVE-2020-8889](https://insights.sbomify.com/CVE-2020-8889/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-9009 and fix it if it is affected.

What it is: CVE-2020-9009 is a low-severity missing authorization vulnerability in n/a, published on 11 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-9009 exists.

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

## Sources

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

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