# CVE-2026-87846: Shipping for Nova Poshta 1.18.7 - 1.19.8 - Unauthenticated Order Shipment Record Deletion

> Unauthenticated attackers can delete arbitrary order shipment records and trigger carrier API calls due to missing authorization checks in the plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/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:** 9 Oct 2026
- **Updated:** 9 Oct 2026
- **Also known as:** GHSA-gvw5-gchw-rwg7

## What is CVE-2026-87846?

CVE-2026-87846 is a medium-severity missing authorization vulnerability in Unknown Shipping for Nova Poshta, published on 9 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Shipping for Nova Poshta WordPress plugin through 1.19.8 does not perform any authorisation, nonce or ownership checks on one of its AJAX actions available to unauthenticated users, allowing anyone to delete the shipment records of arbitrary orders and to make the store issue the carrier's waybill-deletion request for those orders using the store's own stored API credentials.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-87846?


## How do I fix CVE-2026-87846?

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

## Is CVE-2026-87846 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-87846 and fix it if it is affected.

What it is: CVE-2026-87846 is a medium-severity missing authorization vulnerability in Unknown Shipping for Nova Poshta, published on 9 Oct 2026. 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-2026-87846 in the wild and no public exploit code.

Affected product: Unknown Shipping for Nova Poshta. 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-2026-87846/ (Markdown: https://insights.sbomify.com/CVE-2026-87846/index.md)
```

## Sources

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

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