Security readout for executives and security teams
Plain-English summary
CVE-2026-2301 affects the WordPress Post Duplicator plugin through version 3.0.8. A logged-in user with Contributor-level access or higher could add hidden post metadata when duplicating posts. This is an integrity issue, not a full site takeover based on the provided sources.
Executive priority
Treat this as a near-term hygiene fix for WordPress environments with shared authoring access. It is not currently evidenced as mass-exploited, but it can let lower-privileged users alter hidden post behavior.
Technical view
The plugin’s REST duplicate-post handler accepts a customMetaData JSON array and writes directly to wp_postmeta using $wpdb->insert(). This bypasses WordPress add_post_meta() handling and is_protected_meta() checks, allowing lower-privileged authenticated users to set protected meta keys beginning with underscores.
Likely exposure
Exposure is limited to WordPress sites running Post Duplicator up to and including 3.0.8, especially where Contributor or higher roles are assigned to untrusted users.
Exploitation context
The CVSS vector indicates network access, low complexity, low privileges, no user interaction, and limited integrity impact. The source bundle does not show CISA KEV listing or confirmed active exploitation.
Researcher notes
Key issue is missing authorization and protected-meta validation in duplicate_post(). The referenced changeset may indicate remediation work, but the provided bundle does not name a fixed plugin version. Avoid assuming broader impact beyond protected post meta insertion.
Mitigation direction
- Identify WordPress sites using Post Duplicator version 3.0.8 or earlier.
- Check the plugin vendor or WordPress plugin repository for updated guidance.
- Update the plugin if a fixed release is available from the vendor.
- Remove or disable the plugin if it is not business-critical.
- Limit Contributor and higher roles to trusted users only.
- Review duplicated posts for unexpected protected metadata before publishing.
Validation and detection
- Inventory installed Post Duplicator versions across WordPress environments.
- Review users with Contributor, Author, Editor, or Administrator roles.
- Check logs for use of the duplicate-post REST endpoint.
- Inspect recent duplicated posts for unusual underscore-prefixed metadata.
- Confirm remediation against vendor release notes or repository changes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-2301 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/e5c86f72-934c-4f3b-ab2a-65df1490ca8a?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/post-duplicator/tags/3.0.6/includes/api.php#L923CVE reference
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&new=3463768%40post-duplicator%2Ftrunk&old=3459096%40post-duplicator%2Ftrunk&sfp_email=&sfph_mail=CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
