How severe is CVE-2022-4681?

CVE-2022-4681 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2022-4681 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 4% (89th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2022-4681?

CVE-2022-4681 affects Wpwave Hide My Wp. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2022-4681?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2022-4681 published?

CVE-2022-4681 was published on 2023-02-06 and last updated on 2026-06-17.

CVE-2022-4681

CVE-2022-4681 is a critical-severity vulnerability in Wpwave Hide My Wp with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Critical (CVSS 3.x base score 9.8)
EPSS exploit prediction: 4% (89th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Wpwave Hide My Wp
Published: 2023-02-06
Last modified: 2026-06-17

Description

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.

Frequently asked questions

What is CVE-2022-4681?: 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 severe is CVE-2022-4681?: CVE-2022-4681 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2022-4681 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 4% (89th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2022-4681?: CVE-2022-4681 affects Wpwave Hide My Wp. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2022-4681?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2022-4681 published?: CVE-2022-4681 was published on 2023-02-06 and last updated on 2026-06-17.

References

https://wpscan.com/vulnerability/5a4096e8-abe4-41c4-b741-c44e740e8689

Affected products (1)

cpe:2.3:a:wpwave:hide_my_wp:*:*:*:*:*:wordpress:*:*

More vulnerabilities in Wpwave Hide My Wp

CVE-2021-36916 — High (CVSS 8.6): The SQL injection vulnerability in the Hide My WP WordPress plugin (versions <= 6.2.3) is possible because of how the…
CVE-2021-36917 — Medium (CVSS 6.5): WordPress Hide My WP plugin (versions <= 6.2.3) can be deactivated by any unauthenticated user. It is possible to…

All CVEs affecting Wpwave Hide My Wp →