{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-6641 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-6641 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-6641 is a medium-severity vulnerability in astrasecuritysuite WP Hardening (discontinued), published on 18 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-6641 and fix it if it is affected.\n\nWhat it is: CVE-2024-6641 is a medium-severity vulnerability in astrasecuritysuite WP Hardening (discontinued), published on 18 Sep 2024. 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-2024-6641 in the wild and no public exploit code.\n\nAffected product: astrasecuritysuite WP Hardening (discontinued). 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-2024-6641/ (Markdown: https://insights.sbomify.com/CVE-2024-6641/index.md)","id":"CVE-2024-6641","markdown":"https://insights.sbomify.com/CVE-2024-6641/index.md","name":"CVE-2024-6641","record":{"aliases":["GHSA-rxqj-frff-8mf2"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress security plugin","requires_auth":"none","summary":"Unauthenticated attackers can bypass user enumeration protections to expose site usernames due to a flawed regular expression.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"wp_hardening","vendor":"getastra"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-697","name":"Incorrect Comparison"},{"id":"CWE-185","name":"Incorrect Regular Expression"}],"description":"The WP Hardening – Fix Your WordPress Security plugin for WordPress is vulnerable to Security Feature Bypass in all versions up to, and including, 1.2.6. This is due to use of an incorrect regular expression within the \"Stop User Enumeration\" feature. This makes it possible for unauthenticated attackers to bypass intended security restrictions and expose site usernames.","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 Hardening – Fix Your WordPress Security \u003c= 1.2.6 - Unauthenticated Security Feature Bypass to Username Enumeration","id":"CVE-2024-6641","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2024-6642"},"packages":[],"prev":{"headline":"pf incorrectly matches different ICMPv6 states in the state table","id":"CVE-2024-6640"},"products":["WP Hardening (discontinued)"],"published":"2024-09-18","related":[{"cvss_score":6.1,"headline":"WP Hardening \u003c 1.2.2 - Reflected XSS via URI","id":"CVE-2021-24372","kev_date_added":null,"published":"2021-06-21"},{"cvss_score":6.1,"headline":"WP Hardening \u003c 1.2.2 - Reflected XSS via historyvalue","id":"CVE-2021-24373","kev_date_added":null,"published":"2021-06-21"}],"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-08","vendors":["astrasecuritysuite"]},"summary":"Unauthenticated attackers can bypass user enumeration protections to expose site usernames due to a flawed regular expression.","url":"https://insights.sbomify.com/CVE-2024-6641/"}