Security readout for executives and security teams
Plain-English summary
CVE-2026-2893 affects the WordPress Page and Post Clone plugin through version 6.3. A logged-in user with Contributor permissions or higher may be able to read sensitive database information through a SQL injection triggered during post cloning. This is not reported as actively exploited in the provided sources.
Executive priority
Treat as a targeted confidentiality risk. Prioritize WordPress sites with many content contributors, customer data, or sensitive business data in the database. This is not currently supported as an emergency internet-wide exploitation event by the provided sources.
Technical view
The issue is CWE-89 SQL injection in content_clone() via insufficient handling of the meta_key parameter. It is described as second-order: attacker-controlled data is stored as a post meta key and later executed when a post is cloned. CVSS is 6.5, with network access, low complexity, low privileges, and high confidentiality impact.
Likely exposure
Exposure is most likely on WordPress sites running Page and Post Clone versions up to and including 6.3, especially where untrusted users have Contributor-level access or higher. Sites without this plugin, without affected versions, or without such user roles are less likely exposed.
Exploitation context
The provided sources do not indicate known active exploitation or CISA KEV listing. Exploitation requires an authenticated account with Contributor-level privileges or higher. The main business risk is unauthorized database information disclosure, not direct system takeover based on the provided CVSS vector.
Researcher notes
There is a data inconsistency: the narrative names Page and Post Clone, while the affected product entry lists Fast Page & Post Duplicator as default unaffected. Validate against the CVE record, Wordfence entry, and WordPress Trac paths before asset matching or ticket automation.
Mitigation direction
- Identify whether Page and Post Clone is installed and its version.
- If version is 6.3 or earlier, check vendor or WordPress plugin guidance for an update.
- Temporarily disable or remove the plugin if no trusted fix is available.
- Limit Contributor-level access to trusted users only.
- Review whether cloning functionality is business-critical before re-enabling.
Validation and detection
- Inventory WordPress sites for the page-or-post-clone plugin.
- Confirm installed plugin versions against the vulnerable range through 6.3.
- Review users with Contributor, Author, Editor, or Administrator roles.
- Check plugin changelog or vendor guidance for remediation status.
- Monitor for unusual cloning activity by lower-privileged accounts.
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-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. 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 lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-2893 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
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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:H/I:N/A:N2.83.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/85674d8a-96b3-4fae-8bff-900ca78073a4?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/page-or-post-clone/tags/6.3/page-or-post-clone.php#L95CVE reference
- https://plugins.trac.wordpress.org/browser/page-or-post-clone/trunk/page-or-post-clone.php#L95CVE reference
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&new=3474651%40page-or-post-clone%2Ftrunk&old=3202933%40page-or-post-clone%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.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.