WordPress security changelog
MEDIUM CVE-2023-5776 Modified

Post Meta Data Manager: Cross-site request forgery

Post Meta Data Manager is affected by cross-site request forgery. The vulnerable path is reachable without authentication. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.

CVE / CNA score 4.3 CVSS 3.1 · security@wordfence.com
NVD score 8.8 CVSS 3.1 · nvd@nist.gov
Component
Post Meta Data Manager
Plugin slug
post-meta-data-manager
Affected
See vendor advisory
Safe version
See mitigation notes
Published
Nov 21, 2023
Weakness
CWE-352 — Cross-Site Request Forgery (CSRF)

This CVE was published Nov 21, 2023 and is one of 5 known issues for this plugin.

What to do

Update, patch or deactivate.

Update Post Meta Data Manager to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

The Post Meta Data Manager plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.2.1. This is due to missing nonce validation on the pmdm_wp_ajax_delete_meta, pmdm_wp_delete_user_meta, and pmdm_wp_delete_user_meta functions. This makes it possible for unauthenticated attackers to delete arbitrary user, term, and post meta via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

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

References

Primary and upstream sources