# CVE-2023-4792: Duplicate Post Page Menu & Custom Post Type <= 2.3.1 - Missing Authorization to Post Duplication

> Authenticated subscribers can duplicate posts and pages due to missing capability checks in the Duplicate Post Page Menu plugin.

- **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:** 7 Sep 2023
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-794p-vf6q-qrmf

## What is CVE-2023-4792?

CVE-2023-4792 is a medium-severity missing authorization vulnerability in inqsys Duplicate Post Page Menu & Custom Post Type, published on 7 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Duplicate Post Page Menu & Custom Post Type plugin for WordPress is vulnerable to unauthorized page and post duplication due to a missing capability check on the duplicate_ppmc_post_as_draft function in versions up to, and including, 2.3.1. This makes it possible for authenticated attackers with subscriber access or higher to duplicate posts and pages.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Inqsys Duplicate Post Page Menu \& Custom Post Type.

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

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

## Is CVE-2023-4792 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-4792 is a medium-severity missing authorization vulnerability in inqsys Duplicate Post Page Menu & Custom Post Type, published on 7 Sep 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-4792 in the wild and no public exploit code.

Affected product: inqsys Duplicate Post Page Menu & Custom Post Type. 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-4792/ (Markdown: https://insights.sbomify.com/CVE-2023-4792/index.md)
```

## Sources

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

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