CVE-2026-2893 MEDIUM

CVE-2026-2893: Page and Post Clone <= 6.3 - Authenticated (Contributor+) SQL Injection via 'meta_key' Parameter

Vendor Carlosfazenda
Product Fast Page & Post Duplicator
Weakness CWE-89 · SQLi
Published March 5, 2026
Last update April 8, 2026

CVSS base score

6.5/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality High
Integrity None

CVSS vector

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

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

Fast Page & Post Duplicator versions 6.3 and earlier contain a SQL injection vulnerability in a component requiring low-level authentication. An authenticated attacker can craft malicious input to execute arbitrary SQL queries, potentially reading sensitive data from the site's database. Update to a version newer than 6.3 to resolve this issue.

What an attacker can do

03Attacker Capabilities

Read sensitive data from the site database by injecting malicious SQL commands.

Potential impact on your site

04Site Impact

Unauthorized database access could expose user credentials, private posts, or other sensitive information stored in the database.

Conditions required to exploit

05Prerequisites

Attacker must have a low-privilege user account on the site (e.g., subscriber or contributor role).

Key dates

06Disclosure timeline

March 5, 2026 CVE published
April 8, 2026 Record updated