{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-5776 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-5776 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-5776 is a medium-severity vulnerability in gandhihitesh9 Post Meta Data Manager, published on 21 Nov 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-5776 and fix it if it is affected.\n\nWhat it is: CVE-2023-5776 is a medium-severity vulnerability in gandhihitesh9 Post Meta Data Manager, published on 21 Nov 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-5776 in the wild and no public exploit code.\n\nAffected product: gandhihitesh9 Post Meta Data Manager. 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-2023-5776/ (Markdown: https://insights.sbomify.com/CVE-2023-5776/index.md)","id":"CVE-2023-5776","markdown":"https://insights.sbomify.com/CVE-2023-5776/index.md","name":"CVE-2023-5776","record":{"aliases":["GHSA-fm8h-fg2j-xr88"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can delete arbitrary user, term, and post meta by tricking administrators into clicking a link.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"post_meta_data_manager","vendor":"wpexpertplugins"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"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.","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":"Post Meta Data Manager \u003c= 1.2.1 - Cross-Site Request Forgery to Post, Term, and User Meta Deletion","id":"CVE-2023-5776","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2023"},"n_packages":0,"n_references":4,"next":{"headline":"Weintek EasyBuilder Pro Use of Hard-coded Credentials","id":"CVE-2023-5777"},"packages":[],"prev":{"headline":"BackWPup \u003c= 4.0.2 - Plaintext Storage of Backup Destination Password","id":"CVE-2023-5775"},"products":["Post Meta Data Manager"],"published":"2023-11-21","related":[{"cvss_score":8.8,"headline":"Post Meta Data Manager \u003c=1.2.0 - Missing Authorization to Authenticated (Subscriber+) Privilege Escalation","id":"CVE-2023-5425","kev_date_added":null,"published":"2023-10-28"},{"cvss_score":7.5,"headline":"Post Meta Data Manager \u003c=1.2.0 - Missing Authorization to User, Term, and Post Meta Deletion","id":"CVE-2023-5426","kev_date_added":null,"published":"2023-10-28"},{"cvss_score":7.2,"headline":"Post Meta Data Manager \u003c= 1.4.4 - Authentciated (Admin+) Multisite Privilege Escalation","id":"CVE-2024-13835","kev_date_added":null,"published":"2025-03-08"},{"cvss_score":6.4,"headline":"Post Meta Data Manager \u003c= 1.2.3 - Authenticated (Contributor+) Stored Cross-Site Scripting","id":"CVE-2024-6264","kev_date_added":null,"published":"2024-07-02"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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":["gandhihitesh9"]},"summary":"Unauthenticated attackers can delete arbitrary user, term, and post meta by tricking administrators into clicking a link.","url":"https://insights.sbomify.com/CVE-2023-5776/"}