CVE-2022-38058: Authenticated (subscriber+) Plugin Setting change vulnerability in WP Shamsi plugin <= 4.1.1 at WordPress.

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

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

Q: Is CVE-2022-38058 being exploited?

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

CVE-2022-38058 affects wp shamsi. Severity is medium (CVSS 4.3). Authenticated (subscriber+) Plugin Setting change vulnerability in WP Shamsi plugin <= 4.1.1 at WordPress.

Q: How urgent is CVE-2022-38058?

Priority 28/100. No elevated risk signals yet.

Routine

MEDIUM 4.3UPGRADE

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

Authenticated (subscriber+) Plugin Setting change vulnerability in WP Shamsi plugin <= 4.1.1 at WordPress.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	4.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.6% (top 50%)
CISA exploited list	No
Weakness	CWE-264
Published	2022-09-09
Last modified	2026-06-17

Publisher (CNA): Patchstack · 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-09-09 15:15 UTCPublished CVE record published
2026-06-17 04:56 UTCUpdated Record last modified

wpvar wp shamsi UPGRADE

Affected: <= 4.1.1

Fixed in: newer than 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 newer than 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-38058?

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

Is CVE-2022-38058 being exploited?

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

CVE-2022-38058 affects wp shamsi. Severity is medium (CVSS 4.3). Authenticated (subscriber+) Plugin Setting change vulnerability in WP Shamsi plugin <= 4.1.1 at WordPress.

How urgent is CVE-2022-38058?

Priority 28/100. No elevated risk signals yet.

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-4555 MEDIUM 6.5 UPGRADE The WP Shamsi plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on

References

← Back to latest CVEs