CVE-2022-3622

Blog2Social <= 6.9.11 - Missing Authorization to Authenticated (Subscriber+) Settings Update

2022-09-27 00:00

Strategic Overview

Status: Patched in 6.9.12
Affected Plugin: Blog2Social: Social Media Auto Post & Scheduler
Affected Version: <= 6.9.11
CVSS: 4.1Medium
Weakness type: CWE-862 · Missing Authorization
CVE: CVE-2022-3622

View all Blog2Social: Social Media Auto Post & Scheduler vulnerabilities

At a glance

CVE-2022-3622 is a medium-severity Missing Authorization vulnerability in the Blog2Social WordPress plugin, affecting versions <= 6.9.11. It carries a CVSS score of 4.1 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 6.9.12; sites on affected versions should update now. Disclosed September 2022, reported by Marco Wotschka.

Vulnerability Overview

The Blog2Social plugin for WordPress is vulnerable to authorization bypass due to missing capability checks in versions up to, and including, 6.9.11. This makes it possible for authenticated attackers, with subscriber-level permissions and above, to change some plugin settings intended to be modifiable by admins only.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed.

CWE-862: Missing Authorization

Reaching this weakness in Blog2Social <= 6.9.11 takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Blog2Social the fix is 6.9.12: builds <= 6.9.11 are affected, anything from 6.9.12 onward is not.

Remediation

Update to version 6.9.12, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Blog2Social 6.9.12 closes this, and updating the plugin is the step that ends it.

Login Security
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-3622 https://www.wordfence.com/threat-intel/vulnerabilities/id/f5b8d39c-d307-42c9-a972-29b5521a82a4 https://nvd.nist.gov/vuln/detail/CVE-2022-3622

Related records

Same weakness class

Other vulnerabilities in Blog2Social: Social Media Auto Post & Scheduler

CVSS Vector

4.1

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:L/A:N

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredLow
User InteractionRequired
ScopeChanged
ConfidentialityNone
IntegrityLow
AvailabilityNone

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/