# CVE-2023-47754: WordPress Delete Duplicate Posts Plugin <= 4.8.9 is vulnerable to Broken Access Control

> Attackers can access restricted functionality in the Delete Duplicate Posts WordPress plugin due to missing authorization checks.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Dec 2023
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-pc65-vh3q-mh9r

## What is CVE-2023-47754?

CVE-2023-47754 is a medium-severity missing authorization vulnerability in Clever plugins Delete Duplicate Posts, published on 18 Dec 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Missing Authorization vulnerability in Clever plugins Delete Duplicate Posts allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Delete Duplicate Posts: from n/a through 4.8.9.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2023-47754?

It affects 1 product.


Products: Cleverplugins Delete Duplicate Posts.

## How do I fix CVE-2023-47754?

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

## Is CVE-2023-47754 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-47754 and fix it if it is affected.

What it is: CVE-2023-47754 is a medium-severity missing authorization vulnerability in Clever plugins Delete Duplicate Posts, published on 18 Dec 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-47754 in the wild and no public exploit code.

Affected product: Clever plugins Delete Duplicate Posts. 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-2023-47754/ (Markdown: https://insights.sbomify.com/CVE-2023-47754/index.md)
```

## Sources

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

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