# CVE-2026-19077: Copy & Delete Posts < 1.5.5 - Authenticated Arbitrary Post Deletion via Missing Object-Level Authorization

> Authenticated users can permanently delete arbitrary posts belonging to other users due to missing object-level authorization checks in the Duplicate Post plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-47f8-4hph-5246

## What is CVE-2026-19077?

CVE-2026-19077 is a medium-severity missing authorization vulnerability in Unknown Duplicate Post, published on 10 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Duplicate Post WordPress plugin before 1.5.5 does not perform per-object authorisation checks in its bulk copy and delete operations, allowing any user whose role an administrator has granted Duplicate Post WordPress plugin before 1.5.5 access to permanently delete arbitrary posts on the site, including those belonging to other users.

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

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


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

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

## Is CVE-2026-19077 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19077 is a medium-severity missing authorization vulnerability in Unknown Duplicate Post, published on 10 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-19077 in the wild and no public exploit code.

Affected product: Unknown Duplicate Post. 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-19077/ (Markdown: https://insights.sbomify.com/CVE-2026-19077/index.md)
```

## Sources

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

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