CVE-2026-2301

{"id": "CVE-2026-2301", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-2301", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-02-25T21:00:26.768409Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "security@wordfence.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 4.3, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "LOW", "confidentialityImpact": "NONE"}, "impactScore": 1.4, "exploitabilityScore": 2.8}]}, "affected": [{"source": "security@wordfence.com", "affectedData": [{"vendor": "metaphorcreations", "product": "Post Duplicator", "versions": [{"status": "affected", "version": "0", "versionType": "semver", "lessThanOrEqual": "3.0.8"}], "defaultStatus": "unaffected"}]}], "published": "2026-02-25T10:16:18.307", "references": [{"url": "https://plugins.trac.wordpress.org/browser/post-duplicator/tags/3.0.6/includes/api.php#L843", "source": "security@wordfence.com"}, {"url": "https://plugins.trac.wordpress.org/browser/post-duplicator/tags/3.0.6/includes/api.php#L923", "source": "security@wordfence.com"}, {"url": "https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&new=3463768%40post-duplicator%2Ftrunk&old=3459096%40post-duplicator%2Ftrunk&sfp_email=&sfph_mail=", "source": "security@wordfence.com"}, {"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/e5c86f72-934c-4f3b-ab2a-65df1490ca8a?source=cve", "source": "security@wordfence.com"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "security@wordfence.com", "description": [{"lang": "en", "value": "CWE-862"}]}], "descriptions": [{"lang": "en", "value": "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->insert()` 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."}, {"lang": "es", "value": "El plugin Post Duplicator para WordPress es vulnerable a la inserci\u00f3n no autorizada de metadatos de publicaci\u00f3n protegidos arbitrarios en todas las versiones hasta la 3.0.8, inclusive. Esto se debe a que la funci\u00f3n `duplicate_post()` en `includes/api.php` utiliza `$wpdb->insert()` directamente en la tabla `wp_postmeta` en lugar de la funci\u00f3n est\u00e1ndar de WordPress `add_post_meta()`, la cual llamar\u00eda a `is_protected_meta()` para evitar que usuarios con privilegios inferiores establezcan claves de metadatos protegidas (aquellas que comienzan con `_`). Esto hace posible que atacantes autenticados, con acceso de nivel Colaborador o superior, inyecten claves de metadatos de publicaci\u00f3n protegidas arbitrarias como `_wp_page_template`, `_wp_attached_file` y otras claves de metadatos sensibles en publicaciones duplicadas a trav\u00e9s del par\u00e1metro de array JSON `customMetaData` en el endpoint de la API REST `/wp-json/post-duplicator/v1/duplicate-post`."}], "lastModified": "2026-06-17T10:30:44.947", "sourceIdentifier": "security@wordfence.com"}