Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in wpWave Hide My WP hide_my_wp allows Reflected XSS.This issue affects Hide My WP: from n/a through <= 6.2.12.
Product
wordpress hide_my_wp vulnerabilities
6 published CVES affecting wordpress hide_my_wp, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 6
- Critical
- 2
- High
- 2
- Medium
- 2
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest wordpress hide_my_wp CVEs
Newest publication first
-
HighCVSS 7.1 EPSS 0.21%
-
CriticalCVSS 9.8 EPSS 3.8% Public exploit
The Hide My WP WordPress plugin before 6.2.9 does not properly sanitize and escape a parameter before using it in a SQL statement via an AJAX action available to unauthenticated users, leading to a SQL injection.
-
CriticalCVSS 9.8 EPSS 1.9%
The SQL injection vulnerability in the Hide My WP WordPress plugin (versions <= 6.2.3) is possible because of how the IP address is retrieved and used inside a SQL query. The function "hmwp_get_user_ip" tries to retrieve the IP address from multiple headers, including IP address...
-
HighCVSS 7.5 EPSS 2.0%
WordPress Hide My WP plugin (versions <= 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.
-
MediumCVSS 6.1
The Hide My WP plugin for WordPress is vulnerable to Cross-Site Scripting in versions up to, and including, 4.53 due to insufficient input sanitization and output escaping. This makes it possible for attackers to inject arbitrary web scripts that execute in a victim's browser.
-
WORDFENCE-2c889c8e-7546-45bd-884b-7fb0199e595b Hide My WP <= 4.51.1 - Cross-Site Scripting
PublishedMediumCVSS 5.3The Hide My WP plugin for WordPress is vulnerable to Cross-Site Scripting in versions up to, and including, 4.51.1 due to insufficient input sanitization and output escaping. This makes it possible for attackers to inject arbitrary web scripts that execute in a victim's browser.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.