WP Shamsi <= 4.1.0 - Missing Authorization to Arbitrary Plugin Deactivation
Priority LOW 36CWE-862Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- None · Low · Low
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-862.
Summary
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 it matters now
Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00716 54th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2022-4555
- 2026-10-03 Alias added: GHSA-2pq5-28h7-2x78
References
Advisory 2
More wpvar Wp Shamsi vulnerabilities
- TI-2023-00319 WP Shamsi <= 4.3.3 - Subscriber+ Attachment Deletion CVSS 3.1MEDIUM 6.5
- TI-2022-17772 WordPress WP Shamsi plugin <= 4.1.1 - Authenticated Plugin Setting change vulnerability CVSS 3.1MEDIUM 4.3
Sources
- CVE-2022-4555 · CVE Program
- CVE-2022-4555 · NVD
- FIRST EPSS
- GHSA-2pq5-28h7-2x78 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences