Security readout for executives and security teams
Plain-English summary
A vulnerable WP Shamsi WordPress plugin could let an unauthenticated visitor deactivate plugins on the site. The direct impact is limited, but disabling security or defensive plugins can make later attacks easier. Treat this as a meaningful WordPress hardening issue, not a standalone site takeover.
Executive priority
Prioritize remediation for public WordPress sites, especially those relying on security plugins for protection. This is moderate severity because it mainly enables disruption and attack chaining, but it requires no login and can weaken defenses quickly.
Technical view
CVE-2022-4555 is a missing authorization check in WP Shamsi up to and including 4.1.0. The deactivate() function is hooked through init(), allowing unauthenticated requests to deactivate arbitrary WordPress plugins. The CVSS 3.1 score is 6.5 with network access, low complexity, and no privileges required.
Likely exposure
Exposure is limited to WordPress sites running the WP Shamsi plugin at vulnerable versions up to and including 4.1.0. Public WordPress sites are the main concern because the issue requires no authentication or user interaction.
Exploitation context
The source bundle says unauthenticated attackers can deactivate arbitrary plugins, including security plugins, which may aid exploitation of other vulnerabilities. The CVE is not listed as KEV, and the provided sources do not establish active exploitation in the wild.
Researcher notes
The strongest source detail is the missing capability check on deactivate() via init(). Evidence in the bundle supports unauthenticated arbitrary plugin deactivation, but does not provide proof of active exploitation, a specific fixed version, or broader affected products beyond WP Shamsi.
Mitigation direction
- Inventory WordPress sites for the WP Shamsi plugin and installed version.
- Check vendor or WordPress plugin guidance for a fixed release beyond 4.1.0.
- Remove or disable WP Shamsi where no supported fixed version is confirmed.
- Monitor that security plugins remain active after remediation.
- Restrict WordPress administration and plugin management to trusted operators.
Validation and detection
- Confirm whether WP Shamsi is installed on each WordPress site.
- Record plugin versions and flag any instance at 4.1.0 or earlier.
- Review WordPress plugin status for unexpected deactivations.
- Review logs for unusual unauthenticated requests around plugin state changes.
- Verify defensive plugins are active and functioning after remediation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2022-4555 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L3.92.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/7b498c5a-9fd1-43b8-b456-f6cec65d5077?source=cveCVE reference
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=2645044%40wp-shamsi&new=2645044%40wp-shamsi&sfp_email=&sfph_mail=CVE reference
- https://www.wordfence.com/threat-intel/vulnerabilities/id/7b498c5a-9fd1-43b8-b456-f6cec65d5077CVE reference · x_transferred
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.