16 matches found
CVE-2026-24532: Missing Authorization
Missing Authorization vulnerability in SiteLock SiteLock Security – WP Hardening, Login Security & Malware Scans sitelock allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects SiteLock Security – WP Hardening, Login Security & Malware Scans: from n/a through =...
CVE-2025-62128: Missing Authorization
Missing Authorization vulnerability in SiteLock SiteLock Security – WP Hardening, Login Security & Malware Scans sitelock allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects SiteLock Security – WP Hardening, Login Security & Malware Scans: from n/a through =...
EUVD-2021-11285
Malware in sbrugna...
CVE-2024-6641
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...
CVE-2021-24373
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, leading to a reflected Cross-Site Scripting issue...
CVE-2021-24372
The WP Hardening – Fix Your WordPress Security WordPress plugin before 1.2.2 did not sanitise or escape the $SERVER'REQUESTURI' before outputting it in an attribute, leading to a reflected Cross-Site Scripting issue...
CVE-2024-6641
The CVE describes a vulnerability in the WordPress plugin WP Hardening – Fix Your WordPress Security, affecting all versions up to 1.2.6. Root cause: an incorrect regular expression in the Stop User Enumeration feature, enabling unauthenticated attackers to bypass security checks and reveal site ...
CVE-2024-6641: Incorrect Regular Expression
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...
CVE-2021-24373
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, leading to a reflected Cross-Site Scripting issue...
CVE-2021-24373
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, leading to a reflected Cross-Site Scripting issue...
CVE-2021-24373
CVE-2021-24373 affects the WordPress WP Hardening plugin
CVE-2021-24372 WP Hardening < 1.2.2 - Reflected XSS via URI
The WP Hardening – Fix Your WordPress Security WordPress plugin before 1.2.2 did not sanitise or escape the $SERVER'REQUESTURI' before outputting it in an attribute, leading to a reflected Cross-Site Scripting issue...
PT-2021-15908
Name of the Vulnerable Software and Affected Versions WP Hardening – Fix Your WordPress Security versions prior to 1.2.2 Description The issue is related to a reflected Cross-Site Scripting problem. It occurs because the historyvalue GET parameter is not properly sanitised or escaped before being...
PT-2021-15907
Name of the Vulnerable Software and Affected Versions WP Hardening – Fix Your WordPress Security WordPress plugin versions prior to 1.2.2 Description The issue is related to a reflected Cross-Site Scripting problem. It occurs because the $ SERVER'REQUEST URI' is not properly sanitised or escaped...
CVE-2021-24373: Improper Neutralization of Input During Web Page Generation
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, leading to a reflected Cross-Site Scripting issue...
CVE-2021-24372: Improper Neutralization of Input During Web Page Generation
The WP Hardening – Fix Your WordPress Security WordPress plugin before 1.2.2 did not sanitise or escape the $SERVER'REQUESTURI' before outputting it in an attribute, leading to a reflected Cross-Site Scripting issue...