{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-2301 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-2301 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-2301 is a medium-severity missing authorization vulnerability in metaphorcreations Post Duplicator, published on 25 Feb 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-2301 and fix it if it is affected.\n\nWhat it is: CVE-2026-2301 is a medium-severity missing authorization vulnerability in metaphorcreations Post Duplicator, published on 25 Feb 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-2301 in the wild and no public exploit code.\n\nAffected product: metaphorcreations 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-2301/ (Markdown: https://insights.sbomify.com/CVE-2026-2301/index.md)","id":"CVE-2026-2301","markdown":"https://insights.sbomify.com/CVE-2026-2301/index.md","name":"CVE-2026-2301","record":{"aliases":["GHSA-wrj5-2cc6-7p8j"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated contributors can inject arbitrary protected post meta keys via the REST API due to missing authorization checks in the Post Duplicator plugin.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"The Post Duplicator plugin for WordPress is vulnerable to unauthorized arbitrary protected post meta insertion in all versions up to, and including, 3.0.8. This is due to the `duplicate_post()` function in `includes/api.php` using `$wpdb-\u003einsert()` directly to the `wp_postmeta` table instead of WordPress's standard `add_post_meta()` function, which would call `is_protected_meta()` to prevent lower-privileged users from setting protected meta keys (those starting with `_`). This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary protected post meta keys such as `_wp_page_template`, `_wp_attached_file`, and other sensitive meta keys on duplicated posts via the `customMetaData` JSON array parameter in the `/wp-json/post-duplicator/v1/duplicate-post` REST API endpoint.","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":"Missing authorization in Post Duplicator","id":"CVE-2026-2301","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Unsafe Reflection in Mongoid::Criteria.from_hash","id":"CVE-2026-2302"},"packages":[],"prev":{"headline":"BJ Lazy Load \u003c= 1.0.9 - Authenticated (Contributor+) Stored Cross-Site Scripting via Custom HTML Block","id":"CVE-2026-2300"},"products":["Post Duplicator"],"published":"2026-02-25","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":["metaphorcreations"]},"summary":"Authenticated contributors can inject arbitrary protected post meta keys via the REST API due to missing authorization checks in the Post Duplicator plugin.","url":"https://insights.sbomify.com/CVE-2026-2301/"}