CVE-2022-3489: The WP Hide WordPress plugin through 0.0.2 does not have authorisation and CSRF checks in place when updating

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

wp hide: upgrade to newer than 0.0.2. Exact commands for each OS are on this page.

Q: Is CVE-2022-3489 being exploited?

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

CVE-2022-3489 affects wp hide. Severity is medium (CVSS 5.3). The WP Hide WordPress plugin through 0.0.2 does not have authorisation and CSRF checks in place when updating the custom_wpadmin_slug settings, allowing unauthenticated attackers to update it with a crafted request

Q: How urgent is CVE-2022-3489?

Priority 37/100. Public exploit reference; Remotely exploitable, no login, no user action

This week

MEDIUM 5.3REMOTEUPGRADE

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

The WP Hide WordPress plugin through 0.0.2 does not have authorisation and CSRF checks in place when updating the custom_wpadmin_slug settings, allowing unauthenticated attackers to update it with a crafted request

Why this priority

Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.4% (top 68%)
CISA exploited list	No
Weakness	CWE-352, CWE-862
Published	2022-11-07
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: weberge

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

Am I affected?

Timeline

2022-11-07 10:15 UTCPublished CVE record published
2026-06-17 04:59 UTCUpdated Record last modified

weberge wp hide UPGRADE

Affected: <= 0.0.2

Fixed in: newer than 0.0.2

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to newer than 0.0.2 (Debian / Ubuntu)

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

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wp-hide

Note

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

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-3489?

wp hide: upgrade to newer than 0.0.2. Exact commands for each OS are on this page.

Is CVE-2022-3489 being exploited?

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

CVE-2022-3489 affects wp hide. Severity is medium (CVSS 5.3). The WP Hide WordPress plugin through 0.0.2 does not have authorisation and CSRF checks in place when updating the custom_wpadmin_slug settings, allowing unauthenticated attackers to update it with a crafted request

How urgent is CVE-2022-3489?

Priority 37/100. Public exploit reference; Remotely exploitable, no login, no user action

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs