The Duplicate Post WordPress plugin before 1.5.8 does not check that a user duplicating a post is allowed to edit it
Source GCVE Database
Not known to be exploited : upgrade to 1.5.8 soon.
Data as of 14 Nov 2026, 10:02 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 1.5.8
Exploitation evidence
Disclosed: evidence found.
CVE published 14 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.
What to do
Upgrade Duplicate Post (WordPress plugin) to 1.5.8.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Duplicate Post | Affected
| Fixed in
|
AI-suggested
A fix is available in Duplicate Post WordPress plugin version 1.5.8. Users should upgrade to version 1.5.8 or later to address this authorization flaw. Until upgraded, administrators should consider disabling the slug takeover option or restricting plugin access to trusted roles only.
Description
The Duplicate Post WordPress plugin before version 1.5.8 contains an authorization flaw where it does not verify if a user duplicating a post has permission to edit that post. When the slug takeover option is enabled, this allows users with roles granted access by an administrator, such as Contributor, to move any readable post off its original permalink and publish their duplicate at that address.