Unauthenticated plugin deactivation via unchecked capability
Published Dec 16, 2022 · Updated Apr 8, 2026
Missing authorization in WP Shamsi 4.1.0 and earlier allows remote attackers to deactivate arbitrary WordPress plugins. The init-hooked deactivate() function processes a requested plugin without checking the caller's capabilities before deactivation. No authentication is required, and deactivating a security plugin can remove defenses needed to block exploitation of other flaws.
Summary
What happened
Missing authorization in WP Shamsi 4.1.0 and earlier allows remote attackers to deactivate arbitrary WordPress plugins. The init-hooked deactivate() function processes a requested plugin without checking the caller's capabilities before deactivation. No authentication is required, and deactivating a security plugin can remove defenses needed to block exploitation of other flaws.
The record
- CVE
- CVE-2022-4555
- Published
- Dec 16, 2022
- Updated
- Apr 8, 2026
- Vendor
- wpvar
- Product
- WP Shamsi
- Classifications
- CWE-862, T1562.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 16, 2022CVE publishedPublication date reported by the CVE source.
- Apr 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=4.1.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo