Vulnerability Description
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.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Wpvar | Wp Shamsi | < 4.1.1 |
Related Weaknesses (CWE)
References
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&oldThird Party Advisory
- https://www.wordfence.com/threat-intel/vulnerabilities/id/7b498c5a-9fd1-43b8-b45
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&oldThird Party Advisory
- https://www.wordfence.com/threat-intel/vulnerabilities/id/7b498c5a-9fd1-43b8-b45Third Party Advisory
FAQ
What is CVE-2022-4555?
CVE-2022-4555 is a vulnerability with a CVSS score of 6.5 (MEDIUM). 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 ...
How severe is CVE-2022-4555?
CVE-2022-4555 has been rated MEDIUM with a CVSS base score of 6.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2022-4555?
Check the references section above for vendor advisories and patch information. Affected products include: Wpvar Wp Shamsi.