Security readout for executives and security teams
Plain-English summary
CVE-2022-3622 lets logged-in WordPress users with Subscriber-level access or higher change some Blog2Social plugin settings that should be admin-only. The known impact is limited to integrity of plugin configuration, not data theft or service outage. It matters most on sites with open registration or many low-privilege accounts.
Executive priority
Treat as a near-term hygiene fix, not an emergency, unless the site allows public registration or has many untrusted users. Prioritize updating affected WordPress sites and checking configuration integrity.
Technical view
Blog2Social for WordPress through version 6.9.11 lacks required capability checks for some settings update behavior. The CVE maps to CWE-862 and has CVSS 4.1: network reachable, low complexity, low privileges, user interaction required, changed scope, low integrity impact, no confidentiality or availability impact.
Likely exposure
Exposure is limited to WordPress sites running Blog2Social versions up to and including 6.9.11 with authenticated low-privilege users. Public registration, shared contributor programs, or compromised subscriber accounts increase practical risk.
Exploitation context
The bundle does not show CISA KEV listing or active exploitation evidence. Abuse requires an authenticated account and user interaction according to the CVSS vector. Sources only support settings tampering, not full site takeover.
Researcher notes
Focus on missing authorization around settings update paths in Blog2Social. The supplied evidence supports limited integrity impact and CWE-862. Do not infer broader privilege escalation, data exposure, or active exploitation without additional vendor or threat-intelligence confirmation.
Mitigation direction
- Inventory WordPress sites using Blog2Social and identify versions at or below 6.9.11.
- Update Blog2Social beyond the vulnerable range if vendor guidance provides an available fixed release.
- If update is unavailable, restrict low-privilege accounts and review whether the plugin is required.
- Audit Blog2Social settings for unauthorized or unexpected changes.
- Monitor vendor and WordPress plugin guidance for confirmed remediation details.
Validation and detection
- Confirm installed Blog2Social versions across production, staging, and backup WordPress sites.
- Review WordPress user registration and Subscriber account exposure.
- Check plugin settings history or backups for unexpected configuration changes.
- Verify low-privilege users cannot modify admin-only Blog2Social settings after remediation.
- Record that no KEV evidence is present in the supplied source bundle.
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-3622 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.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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:R/S:C/C:N/I:L/A:N2.31.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.1MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/f5b8d39c-d307-42c9-a972-29b5521a82a4?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/blog2social/tags/6.9.10/includes/B2S/Settings/Item.php#L116CVE reference
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=2795052%40blog2social&new=2795052%40blog2social&sfp_email=&sfph_mail=CVE reference
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=2796598%40blog2social&new=2796598%40blog2social&sfp_email=&sfph_mail=CVE reference
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.