Security readout for executives and security teams
Plain-English summary
A logged-in low-privileged WordPress user could change WP Shamsi plugin settings. This may alter site behavior or configuration, but the sources do not show data theft, outage, or unauthenticated access. Risk is higher on sites with public registration or many subscriber accounts.
Executive priority
Handle in normal vulnerability remediation cycles, escalating for public-registration WordPress sites or environments with many untrusted users. The business concern is unauthorized configuration change, not confirmed compromise or service outage.
Technical view
WP Shamsi for WordPress versions <= 4.1.1 has an authenticated plugin setting change vulnerability. CVSS 3.1 is 4.3: network exploitable, low complexity, low privileges required, no user interaction, unchanged scope, and low integrity impact only.
Likely exposure
Exposure is limited to WordPress installations running WP Shamsi <= 4.1.1, especially where subscriber or other low-privileged accounts exist. Sites without the plugin or without untrusted authenticated users are less exposed.
Exploitation context
The provided sources and KEV status do not indicate known active exploitation. The vulnerability requires an authenticated subscriber-level or higher account, so abuse depends on account access or open registration.
Researcher notes
Evidence identifies an authenticated setting-change issue with CWE-264 and low integrity impact. The bundle does not include exploit details, patch version, affected code path, or proof of active exploitation, so validation should focus on version, roles, and vendor guidance.
Mitigation direction
- Check vendor and WordPress plugin guidance for a fixed release.
- Update WP Shamsi if a non-affected version is available.
- Disable or remove WP Shamsi if it is not required.
- Restrict public registration and remove unnecessary low-privileged accounts.
- Review WP Shamsi settings for unauthorized changes.
Validation and detection
- Inventory WordPress sites for the WP Shamsi plugin.
- Confirm installed WP Shamsi versions are above 4.1.1 or remediated.
- Check whether subscriber-level users can access plugin setting changes.
- Review recent admin and plugin-setting activity for anomalies.
- Verify public registration and default user roles are appropriate.
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-264: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookupCVE-2022-38058 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
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
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:L/UI:N/S:U/C:N/I:L/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/vulnerability/wp-shamsi/wordpress-wp-shamsi-plugin-4-1-1-authenticated-plugin-setting-change-vulnerability/_s_id=cveCVE reference · x_refsource_CONFIRM
- https://wordpress.org/plugins/wp-shamsi/#developersCVE reference · x_refsource_CONFIRM
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.
Permissions, Privileges, and Access Controls
Permissions, Privileges, and Access Controls represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.