Skip to main content

Blog2Social CVE-2026-89029

| EUVDEUVD-2026-80769 MEDIUM
Authorization Bypass Through User-Controlled Key (CWE-639)
2026-09-16 VulnCheck GHSA-6r37-32vj-mjwv
5.3
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as edit_posts user
  2. Delivery
    Send b2s_get_select_mandant_user AJAX request
  3. Exploit
    Iterate owner parameter over user IDs
  4. Execution
    Resolve IDs to display names
  5. Impact
    Enumerate valid accounts for follow-on attacks

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
Exploitation Conditions

Requires an authenticated WordPress account with the edit_posts capability (Contributor, Author, Editor, or Administrator role) on a site running Blog2Social before 9.1.0; the attacker sends requests to the b2s_get_select_mandant_user AJAX handler supplying arbitrary IDs in the owner parameter. Limiting factors: it is NOT remotely unauthenticated - a valid low-privileged login is needed, so risk is highest on sites allowing open/self registration or with many low-trust contributor accounts. Impact is limited to disclosure of user IDs, display names, and account existence; no data modification, code execution, or service disruption is possible.

Impact

This is a genuine but low-severity information-exposure issue, correctly rated CVSS 4.0 5.3 (Medium). The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) confirms network-reachable, low-complexity exploitation but requires authentication as a low-privileged user holding the edit_posts capability (Author/Contributor/Editor role) - this is NOT unauthenticated. Impact is confidentiality-only and LOW (VC:L, VI:N, VA:N): the attacker learns user IDs, display names, and account existence, but gains no write, code-execution, or availability impact. Exploitation status: no public exploit identified at time of analysis - VulnCheck published an advisory but no POC or KEV listing, and EPSS is not provided. There are no conflicting signals: description, CWE-639 (authorization bypass / IDOR on user data), and CVSS all align. This is a real, patch-worthy authorization defect but a low-priority one - useful for reconnaissance (e.g., harvesting valid usernames like the admin account to seed brute-force or phishing) rather than direct compromise. Note the input 'Authentication Bypass' tag is misleading: this requires authentication and is an authorization/enumeration flaw, not an auth bypass.

Exploit ScenarioDerived

A low-privileged authenticated user (e.g., a Contributor or Author account, possibly obtained via open registration or a compromised low-tier account) sends crafted b2s_get_select_mandant_user AJAX requests iterating the owner parameter over user IDs. The handler resolves each ID to a display name without an authorization check, letting the attacker enumerate all WordPress accounts and confirm which IDs exist. No public POC is currently identified, but exploitation is trivial given the low complexity.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 16, 2026

User account enumeration in the Adenion Blog2Social plugin for WordPress before 9.1.0 lets any authenticated user holding the edit_posts capability - such as a Contributor, Author, Editor, or Administrator - resolve arbitrary numeric user IDs to their display names and confirm whether those accounts exist. The bug is an authorization bypass through a user-controlled key (CWE-639) in the b2s_get_select_mandant_user AJAX handler, which returns user data for the attacker-supplied owner parameter without checking that the caller is allowed to read account information; the CVSS 4.0 base score is 5.3 (Medium) and the assessed CVSS 3.1 vector is AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N, meaning confidentiality-only impact with no modification or availability effect. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation; practical risk is concentrated on sites that allow open or self-registration or that host many low-trust contributor accounts, since a valid low-privileged login is a strict prerequisite.

RemediationAI

Vendor-released patch: 9.1.0 - upgrade Blog2Social to 9.1.0 or later through the WordPress admin Plugins screen (or the plugin page at https://wordpress.org/plugins/blog2social/#developers) and confirm the version string in the Plugins list before considering the finding closed; patching is the only complete fix because it restores the missing authorization check in b2s_get_select_mandant_user. If the update cannot be applied immediately, the most effective compensating control is to eliminate the prerequisite rather than the symptom: disable or tightly gate open/self-registration so that untrusted parties cannot obtain an edit_posts-capable account, and audit existing Contributor/Author accounts, removing or downgrading any that are not business-justified - with the trade-off that this restricts collaboration workflows that legitimately depend on those roles. A narrower option is a WAF or ModSecurity rule that rejects POSTs to /wp-admin/admin-ajax.php when the action parameter equals b2s_get_select_mandant_user, but this is brittle (the plugin's own admin UI may issue the same action, so social-sharing screens can break) and it is bypassable if the attacker can reach the endpoint by another path, so it should be treated as temporary only. Disabling the plugin entirely removes the exposure at the cost of losing its social-media publishing and scheduling functionality, and should be considered when the site runs many low-trust contributor accounts. Also note that this weakness leaks user IDs, display names, and account existence, which can feed credential-guessing and social-engineering campaigns even though no data is modified, so log review for repeated requests with sequential owner values is a reasonable detection measure. Refer to the VulnCheck advisory (https://www.vulncheck.com/advisories/blog2social-wordpress-plugin-user-enumeration-via-ajax-handler) for the original report and to the WordPress.org plugin changelog for the 9.1.0 release details.

Affected VersionsENISA

Blog2Social 0 <9.1.0

Affected Packages

euvd blog2social fix: 9.1.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Blog2Social is a PHP-based WordPress plugin that registers AJAX handlers and exposes them through the standard WordPress admin-ajax.php endpoint using the action parameter, where the handler function b2s_get_select_mandant_user lives in includes/Ajax/Get.php. That handler accepts a client-supplied owner value and resolves it into a WordPress user display name, but it never verifies current_user_can() style permissions or confirms that the requesting account is entitled to read the target account's data - a textbook instance of CWE-639, Authorization Bypass Through User-Controlled Key (IDOR), in which the object identifier is taken directly from request input and trusted for the subsequent lookup. Because the request is served over the network with no user interaction and the only barrier is a low-privileged authenticated session (CVSS 4.0 PR:L, assessed CVSS 3.1 PR:L), the plugin's role is limited to anonymous-browsing-proof disclosure: an attacker who already possesses an edit_posts-capable account can iterate IDs and build a map of user IDs to display names plus account-existence confirmations. The supplied CPE cpe:2.3:a:adenion:blog2social:*:*:*:*:*:*:*:* uses a wildcard version, indicating every release before the fixed 9.1.0 build is affected regardless of platform, PHP version, or WordPress version, and the accompanying tags (PHP, WordPress, Blog2Social, Adenion, and a vendor-style 'Authentication Bypass' label) should be read carefully: this is an authorization/information-exposure weakness requiring a valid login, not an unauthenticated authentication bypass. The independent assessment confirms the same scope - no data modification, no code execution, no service disruption - and the CVSS 4.0 vector (VC:L, VI:N, VA:N, all subsequent-system metrics N) matches that limited confidentiality-only view.

Know when Blog2Social gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulnCheck) PRIMARY 5.3 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
vuln.today AI 4.3 MEDIUM

Network-reachable AJAX endpoint with low complexity but requires an authenticated edit_posts user (PR:L); impact is limited to low confidentiality (user enumeration), so I:N and A:N.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

Adenion Blog2Social plugin for WordPress before 9.1.0 allows low-privileged users to enumerate WordPress user accounts. The b2s_get_select_mandant_user AJAX handler in includes/Ajax/Get.php resolves arbitrary user IDs supplied in the owner parameter to display names without verifying that the caller is authorized to read user account data, allowing any user with the edit_posts capability to map WordPress user IDs to display names and confirm account existence for arbitrary IDs.

Threat Intelligence Overview

EPSS Score
0.3%
Top 81% exploitable
Prevalence
High
Blog2Social is a widely installed WordPress social-sharing plugin, hundreds of thousands of active installs
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
High

Priority Score

26
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

CVE-2022-3246 HIGH POC
8.8 Oct 25

The Blog2Social: Social Media Auto Post & Scheduler WordPress plugin before 6.9.10 does not properly sanitise and escape

CVE-2021-24137 HIGH POC
8.8 Mar 18

Unvalidated input in the Blog2Social WordPress plugin, versions before 6.3.1, lead to SQL Injection in the Re-Share Post

CVE-2022-3247 MEDIUM POC
6.5 Oct 25

The Blog2Social: Social Media Auto Post & Scheduler WordPress plugin before 6.9.10 does not have authorisation in an AJA

CVE-2023-3936 MEDIUM POC
6.1 Aug 21

The Blog2Social WordPress plugin before 7.2.1 does not sanitise and escape a parameter before outputting it back in the

CVE-2021-24956 MEDIUM POC
6.1 Dec 21

The Blog2Social: Social Media Auto Post & Scheduler WordPress plugin before 6.8.7 does not sanitise and escape the b2sSh

CVE-2019-9576 MEDIUM POC
6.1 Mar 05

The Blog2Social plugin before 5.0.3 for WordPress allows wp-admin/admin.php?page=blog2social-ship XSS. Rated medium seve

CVE-2024-3549 CRITICAL
9.9 Jun 11

The Blog2Social: Social Media Auto Post & Scheduler plugin for WordPress is vulnerable to SQL Injection via the 'b2sSort

CVE-2019-13572 CRITICAL
9.8 Aug 01

The Adenion Blog2Social plugin through 5.5.0 for WordPress allows SQL Injection. Rated critical severity (CVSS 9.8), thi

CVE-2023-40554 MEDIUM
6.1 Sep 06

Unauth. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, low at

CVE-2019-17550 MEDIUM
6.1 Nov 13

The Blog2Social plugin before 5.9.0 for WordPress is affected by: Cross Site Scripting (XSS). Rated medium severity (CVS

CVE-2026-7051 MEDIUM
5.4 May 13

Blog2Social: Social Media Auto Post & Scheduler plugin for WordPress versions up to 8.9.0 allows authenticated attackers

CVE-2024-7302 MEDIUM
5.4 Aug 01

The Blog2Social: Social Media Auto Post & Scheduler plugin for WordPress is vulnerable to Stored Cross-Site Scripting vi

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy