{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-36917 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-36917 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-36917 is a medium-severity missing authorization vulnerability in wpWave Hide My WP (WordPress plugin), published on 24 Nov 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-36917 and fix it if it is affected.\n\nWhat it is: CVE-2021-36917 is a medium-severity missing authorization vulnerability in wpWave Hide My WP (WordPress plugin), published on 24 Nov 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-36917 in the wild and no public exploit code.\n\nAffected product: wpWave Hide My WP (WordPress plugin). 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-36917/ (Markdown: https://insights.sbomify.com/CVE-2021-36917/index.md)","id":"CVE-2021-36917","markdown":"https://insights.sbomify.com/CVE-2021-36917/index.md","name":"CVE-2021-36917","record":{"aliases":["GHSA-g6pf-m72v-9jx7"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can deactivate the Hide My WP plugin by retrieving a reset token, bypassing security protections.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Patchstack","cpe":[{"product":"hide_my_wp","vendor":"wpwave"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"},{"id":"CWE-284","name":"Improper Access Control"}],"description":"WordPress Hide My WP plugin (versions \u003c= 6.2.3) can be deactivated by any unauthenticated user. It is possible to retrieve a reset token which can then be used to deactivate the plugin.","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":"WordPress Hide My WP premium plugin \u003c= 6.2.3 - Unauthenticated Plugin Deactivation vulnerability","id":"CVE-2021-36917","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2021"},"n_packages":0,"n_references":3,"next":{"headline":"WordPress Awesome Support plugin \u003c= 6.0.6 - Multiple Authenticated Reflected Cross-Site Scripting (XSS) vulnerabilities","id":"CVE-2021-36919"},"packages":[],"prev":{"headline":"WordPress Hide My WP premium plugin \u003c= 6.2.3 - Unauthenticated SQL injection (SQLi) vulnerability","id":"CVE-2021-36916"},"products":["Hide My WP (WordPress plugin)"],"published":"2021-11-24","related":[{"cvss_score":9.8,"headline":"Hide My WP \u003c 6.2.9 - Unauthenticated SQLi","id":"CVE-2022-4681","kev_date_added":null,"published":"2023-02-06"},{"cvss_score":8.6,"headline":"WordPress Hide My WP premium plugin \u003c= 6.2.3 - Unauthenticated SQL injection (SQLi) vulnerability","id":"CVE-2021-36916","kev_date_added":null,"published":"2021-11-24"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-28","vendors":["wpWave"]},"summary":"Unauthenticated attackers can deactivate the Hide My WP plugin by retrieving a reset token, bypassing security protections.","url":"https://insights.sbomify.com/CVE-2021-36917/"}