CVE-2022-4555: The WP Shamsi plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on

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

wp shamsi: upgrade to 4.1.1. Exact commands for each OS are on this page.

Q: Is CVE-2022-4555 being exploited?

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

CVE-2022-4555 affects wp shamsi. Severity is medium (CVSS 6.5). The WP Shamsi plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on the deactivate() function hooked via init() in versions up to, and including, 4.1.0. This makes it possible for unauthenticated at

Q: How urgent is CVE-2022-4555?

Priority 41/100. Remotely exploitable, no login, no user action

This month

MEDIUM 6.5REMOTEUPGRADE

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

The WP Shamsi plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on the deactivate() function hooked via init() in versions up to, and including, 4.1.0. This makes it possible for unauthenticated attackers to deactivate arbitrary plugins on the site. This can be used to deactivate security plugins that aids in exploiting other vulnerabilities.

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.7% (top 46%)
CISA exploited list	No
Weakness	CWE-862
Published	2022-12-16
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: wpvar

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

Am I affected?

Timeline

2022-12-16 14:15 UTCPublished CVE record published
2026-06-17 05:21 UTCUpdated Record last modified

wpvar wp shamsi UPGRADE

Affected: < 4.1.1

Fixed in: 4.1.1

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to 4.1.1 (Debian / Ubuntu)

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

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wp-shamsi

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

wp shamsi: upgrade to 4.1.1. Exact commands for each OS are on this page.

Is CVE-2022-4555 being exploited?

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

CVE-2022-4555 affects wp shamsi. Severity is medium (CVSS 6.5). The WP Shamsi plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on the deactivate() function hooked via init() in versions up to, and including, 4.1.0. This makes it possible for unauthenticated at

How urgent is CVE-2022-4555?

Priority 41/100. Remotely exploitable, no login, no user action

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2023-0335 MEDIUM 6.5 UPGRADE The WP Shamsi WordPress plugin through 4.3.3 has CSRF and broken access control vulnerabilities which leads us
CVE-2022-38058 MEDIUM 4.3 UPGRADE Authenticated (subscriber+) Plugin Setting change vulnerability in WP Shamsi plugin <= 4.1.1 at WordPress.

References

← Back to latest CVEs