Getastra develops WordPress hardening and security tooling, with its vulnerability profile centered on this focused product line and the application-layer input-handling issues that arise in web-facing defensive software. The recurring weakness classes—cross-site scripting, incorrect comparison logic, and improper regular expression handling—reflect the input-validation and filtering demands inherent to a WordPress security plugin. Current severity, exploitation status, and detailed exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Getastra over time
Signals from CVEs in this vendor scope (3 CVEs).
3 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2021-24373MEDIUM The WP Hardening – Fix Your WordPress Security WordPress plugin before 1.2.2 did not sanitise or escape the historyvalue GET parameter before outputting it in a Javascript block, l | Jun 21, 2021 | 6.1 | 20 | NO | NO |
CVE-2021-24372MEDIUM The WP Hardening – Fix Your WordPress Security WordPress plugin before 1.2.2 did not sanitise or escape the $_SERVER['REQUEST_URI'] before outputting it in an attribute, leading to | Jun 21, 2021 | 6.1 | 20 | NO | NO |
CVE-2024-6641MEDIUM 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 i | Sep 18, 2024 | 5.3 | 16 | NO | NO |
Signals from CVEs in this vendor scope (3 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Getastra.
Media articles that mention a CVE ID that affects a product developed by Getastra — matched by CVE ID, not by vendor name.