dbcve.org
Wp ShamsiWordPress extension · Wpvar

CVE-2022-4555

MEDIUM · 5.3 CVSS v3.1 Published 2022-12-16
Fix available
A fix is available. Upgrade to 4.1.1 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The WP Shamsi plugin for WordPress versions up to 4.1.0 has a missing capability check on the deactivate() function hooked via init(). This allows unauthenticated attackers to send requests that deactivate arbitrary plugins on the site, including security plugins, creating a pathway to exploit other vulnerabilities.

MitigationUpdate the WP Shamsi plugin to version 4.1.1 or later which includes proper capability checks on the deactivate() function. Until the update is applied, consider deactivating the plugin or implementing WAF rules to block requests targeting the plugin's deactivate functionality.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Wp ShamsiWordPress extension
Affected:< 4.1.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify WP Shamsi plugin is installed
    Check the wp-content/plugins directory for a folder named 'wp-shamsi' or 'shamsi-date', or use WP-CLI: wp plugin list --status=active --format=csv
    Affected if The plugin folder exists in wp-content/plugins/ and the plugin is active
  2. Identify installed version
    Read the plugin header from wp-content/plugins/wp-shamsi/wp-shamsi.php (or main plugin file) to find the 'Version:' field, or run: wp plugin get wp-shamsi --format=json
    Affected if Version is less than 4.1.1 (e.g., 4.1.0, 4.0.x, etc.)
  3. Confirm vulnerable function exists
    Inspect the main plugin PHP file for a function named deactivate() hooked via add_action('init', 'deactivate') or similar, or check for any public function handling plugin deactivation without a capability check
    Affected if A deactivate function hooked to init() is present without current_user_can() or a capability check before performing the deactivation action

If WP Shamsi is installed with a version below 4.1.1 and contains an unprotected deactivate function hooked to init(), the site is affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.1.1 or later
Fixed in 4.1.1
Interim mitigation

Update the WP Shamsi plugin to version 4.1.1 or later which includes proper capability checks on the deactivate() function. Until the update is applied, consider deactivating the plugin or implementing WAF rules to block requests targeting the plugin's deactivate functionality.

Recommended fix High confidence

WP Shamsi version 4.1.1

  1. 1. Create a full backup of the WordPress site (database and files) before making any changes
  2. 2. Navigate to the WordPress admin dashboard
  3. 3. Go to Plugins > Installed Plugins
  4. 4. Locate the 'WP Shamsi' plugin in the list
  5. 5. Click 'Update now' if an update is available, or manually upload version 4.1.1 from the WordPress plugin repository
  6. 6. Verify the plugin is running version 4.1.1 or later after updating
  7. 7. Test that the plugin functionality still works as expected
  8. 8. Verify that other plugins (especially security plugins) are still active

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wp Shamsi Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-4555 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-4555 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data