{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-2893 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-2893 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-2893 is a medium-severity SQL injection vulnerability in carlosfazenda Fast Page \u0026 Post Duplicator, published on 5 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-2893 and fix it if it is affected.\n\nWhat it is: CVE-2026-2893 is a medium-severity SQL injection vulnerability in carlosfazenda Fast Page \u0026 Post Duplicator, published on 5 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-2893 in the wild and no public exploit code.\n\nAffected product: carlosfazenda Fast Page \u0026 Post Duplicator. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-2893/ (Markdown: https://insights.sbomify.com/CVE-2026-2893/index.md)","id":"CVE-2026-2893","markdown":"https://insights.sbomify.com/CVE-2026-2893/index.md","name":"CVE-2026-2893","record":{"aliases":["GHSA-3xm9-wqg6-2qvm"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated contributors can exploit SQL injection in the Page and Post Clone plugin to extract sensitive database information via the meta_key parameter.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Page and Post Clone \u003c= 6.3 - Authenticated (Contributor+) SQL Injection via 'meta_key' Parameter","id":"CVE-2026-2893","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"funadmin forget.html getMember information disclosure","id":"CVE-2026-2894"},"packages":[],"prev":{"headline":"Otter Blocks \u003c= 3.1.4 - Improper Authorization to Unauthenticated Purchase Verification Bypass via Forged Cookie","id":"CVE-2026-2892"},"products":["Fast Page \u0026 Post Duplicator"],"published":"2026-03-05","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["carlosfazenda"]},"summary":"Authenticated contributors can exploit SQL injection in the Page and Post Clone plugin to extract sensitive database information via the meta_key parameter.","url":"https://insights.sbomify.com/CVE-2026-2893/"}