CVE-2022-4681: The Hide My WP WordPress plugin before 6.2.9 does not properly sanitize and escape a parameter before using it

Q: How do I fix CVE-2022-4681?

hide my wp: upgrade to 6.2.9. Exact commands for each OS are on this page.

Q: Is CVE-2022-4681 being exploited?

CVE-2022-4681 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-4681 affect?

CVE-2022-4681 affects hide my wp. Severity is critical (CVSS 9.8). 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.

Q: How urgent is CVE-2022-4681?

Priority 67/100. Critical severity; EPSS top 10%: very likely to be exploited; Public exploit reference; Remotely exploitable, no login, no user action

This week

CRITICAL 9.8REMOTEUPGRADE

CVE-2022-4681 is a critical-severity flaw (CVSS 9.8) affecting hide my wp. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Critical severity
EPSS top 10%: very likely to be exploited
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	3.8% (top 10%)
CISA exploited list	No
Published	2023-02-06
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: wpwave

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2023-02-06 20:15 UTCPublished CVE record published
2026-06-17 05:21 UTCUpdated Record last modified

wpwave hide my wp UPGRADE

Affected: < 6.2.9

Fixed in: 6.2.9

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy hide-my-wp || rpm -q hide-my-wp || hide-my-wp --version

2. UPGRADE to 6.2.9 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade hide-my-wp

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade hide-my-wp

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Exploit-DB: Hide My WP < 6.2.9 - Unauthenticated SQLi

Verify at the official source NVD · CVE Program · Report a problem with this page
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-4681?

hide my wp: upgrade to 6.2.9. Exact commands for each OS are on this page.

Is CVE-2022-4681 being exploited?

CVE-2022-4681 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-4681 affect?

CVE-2022-4681 affects hide my wp. Severity is critical (CVSS 9.8). 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.

How urgent is CVE-2022-4681?

Priority 67/100. Critical severity; EPSS top 10%: very likely to be exploited; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs