Home

Description

The Page and Post Clone plugin for WordPress is vulnerable to SQL Injection via the 'meta_key' parameter in the content_clone() function in all versions up to, and including, 6.3. This is due to insufficient escaping on the user-supplied meta_key value and insufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Contributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. The injection is second-order: the malicious payload is stored as a post meta key and executed when the post is cloned.

PUBLISHED Reserved 2026-02-20 | Published 2026-03-05 | Updated 2026-03-05 | Assigner Wordfence




MEDIUM: 6.5CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Problem types

CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Product status

Default status
unaffected

* (semver)
affected

Timeline

2026-03-04:Disclosed

Credits

Arthur GRIMAULT finder

References

www.wordfence.com/...-96b3-4fae-8bff-900ca78073a4?source=cve

plugins.trac.wordpress.org/...ags/6.3/page-or-post-clone.php

plugins.trac.wordpress.org/...e/trunk/page-or-post-clone.php

plugins.trac.wordpress.org/...%2Ftrunk&sfp_email=&sfph_mail=

cve.org (CVE-2026-2893)

nvd.nist.gov (CVE-2026-2893)

Download JSON