PatchTheCVECVE-2022-2538: The WP Hide & Security Enhancer WordPress plugin before 1.8 does not escape a parameter before outputting it b
CVE-2022-2538 is a medium-severity flaw (CVSS 6.1) affecting wp hide \& security enhancer. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The WP Hide & Security Enhancer WordPress plugin before 1.8 does not escape a parameter before outputting it back in an attribute of a backend page, leading to a Reflected Cross-Site Scripting
Why this priority
- Public exploit reference
A fixed release or distro patch exists.
Risk facts
| CVSS score | 6.1 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | Required |
| EPSS exploit chance | 0.7% (top 48%) |
| CISA exploited list | No |
| Weakness | CWE-79 |
| Published | 2022-08-29 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2022-2538?
wp hide \& security enhancer: upgrade to 1.8. Exact commands for each OS are on this page.
Is CVE-2022-2538 being exploited?
CVE-2022-2538 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2022-2538 affect?
CVE-2022-2538 affects wp hide \& security enhancer. Severity is medium (CVSS 6.1). The WP Hide & Security Enhancer WordPress plugin before 1.8 does not escape a parameter before outputting it back in an attribute of a backend page, leading to a Reflected Cross-Site Scripting
How urgent is CVE-2022-2538?
Priority 39/100. Public exploit reference