{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-4385 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-4385 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-4385 is a medium-severity vulnerability in nimeshrmr WP Private Content Plus, published on 1 Jul 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-2021-4385 and fix it if it is affected.\n\nWhat it is: CVE-2021-4385 is a medium-severity vulnerability in nimeshrmr WP Private Content Plus, published on 1 Jul 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-2021-4385 in the wild and no public exploit code.\n\nAffected product: nimeshrmr WP Private Content Plus. 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-2021-4385/ (Markdown: https://insights.sbomify.com/CVE-2021-4385/index.md)","id":"CVE-2021-4385","markdown":"https://insights.sbomify.com/CVE-2021-4385/index.md","name":"CVE-2021-4385","record":{"aliases":["GHSA-m34p-w2ph-8hgm"],"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 add group members via CSRF if an admin clicks a link, requiring an upgrade to the WP Private Content Plus plugin.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"wp_private_content_plus","vendor":"wpexpertdeveloper"}],"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 WP Private Content Plus plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.1. This is due to missing or incorrect nonce validation on the save_groups() function. This makes it possible for unauthenticated attackers to add new group members 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":"WP Private Content Plus \u003c= 3.1 - Cross-Site Request Forgery Bypass","id":"CVE-2021-4385","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2021"},"n_packages":0,"n_references":9,"next":{"headline":"WP Security Question \u003c= 1.0.5 - Cross-Site Request Forgery Bypass","id":"CVE-2021-4386"},"packages":[],"prev":{"headline":"WordPress Photo Gallery – Image Gallery \u003c= 1.0.6 - Cross-Site Request Forgery Bypass","id":"CVE-2021-4384"},"products":["WP Private Content Plus"],"published":"2023-07-01","related":[{"cvss_score":7.5,"headline":"Missing authorization in n/a","id":"CVE-2019-15816","kev_date_added":null,"published":"2019-08-30"},{"cvss_score":5.3,"headline":"WP Private Content Plus \u003c= 3.6 - Protection Mechanism Bypass","id":"CVE-2024-0680","kev_date_added":null,"published":"2024-02-28"}],"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":"total"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["nimeshrmr"]},"summary":"Unauthenticated attackers can add group members via CSRF if an admin clicks a link, requiring an upgrade to the WP Private Content Plus plugin.","url":"https://insights.sbomify.com/CVE-2021-4385/"}