{"resultsPerPage":1,"startIndex":0,"totalResults":1,"format":"NVD_CVE","version":"2.0","timestamp":"2026-04-17T21:00:55.493","vulnerabilities":[{"cve":{"id":"CVE-2026-2893","sourceIdentifier":"security@wordfence.com","published":"2026-03-05T08:15:59.963","lastModified":"2026-03-05T19:38:33.877","vulnStatus":"Awaiting Analysis","cveTags":[],"descriptions":[{"lang":"en","value":"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."},{"lang":"es","value":"El plugin Page and Post Clone para WordPress es vulnerable a inyección SQL a través del parámetro 'meta_key' en la función content_clone() en todas las versiones hasta la 6.3, inclusive. Esto se debe a un escape insuficiente del valor 'meta_key' proporcionado por el usuario y a una preparación insuficiente en la consulta SQL existente. Esto permite a atacantes autenticados, con acceso de nivel Colaborador o superior, añadir consultas SQL adicionales a consultas ya existentes que pueden usarse para extraer información sensible de la base de datos. La inyección es de segundo orden: la carga útil maliciosa se almacena como una clave meta de publicación y se ejecuta cuando se clona la publicación."}],"metrics":{"cvssMetricV31":[{"source":"security@wordfence.com","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","baseScore":6.5,"baseSeverity":"MEDIUM","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"NONE","availabilityImpact":"NONE"},"exploitabilityScore":2.8,"impactScore":3.6}]},"weaknesses":[{"source":"security@wordfence.com","type":"Secondary","description":[{"lang":"en","value":"CWE-89"}]}],"references":[{"url":"https://plugins.trac.wordpress.org/browser/page-or-post-clone/tags/6.3/page-or-post-clone.php#L95","source":"security@wordfence.com"},{"url":"https://plugins.trac.wordpress.org/browser/page-or-post-clone/trunk/page-or-post-clone.php#L95","source":"security@wordfence.com"},{"url":"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=","source":"security@wordfence.com"},{"url":"https://www.wordfence.com/threat-intel/vulnerabilities/id/85674d8a-96b3-4fae-8bff-900ca78073a4?source=cve","source":"security@wordfence.com"}]}}]}