CVE-2026-1942: CWE-862 Missing Authorization in pr-gateway Blog2Social: Social Media Auto Post & Scheduler
The Blog2Social: Social Media Auto Post & Scheduler plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the b2s_curation_draft AJAX action in all versions up to, and including, 8.7.4. The curationDraft() function only verifies current_user_can('read') without checking whether the user has edit_post permission for the target post. Combined with the plugin granting UI access and nonce exposure to all roles, this makes it possible for authenticated attackers, with Subscriber-level access and above, to overwrite the title and content of arbitrary posts and pages by supplying a target post ID via the 'b2s-draft-id' parameter.
AI Analysis
Technical Summary
CVE-2026-1942 is a missing authorization vulnerability (CWE-862) found in the Blog2Social: Social Media Auto Post & Scheduler WordPress plugin, affecting all versions up to 8.7.4. The vulnerability exists in the AJAX action 'b2s_curation_draft', where the curationDraft() function improperly checks user capabilities by only verifying if the user has 'read' permission rather than the more restrictive 'edit_post' permission for the targeted post. Because the plugin grants UI access and nonce exposure to all user roles, including Subscribers, an authenticated attacker with minimal privileges can exploit this flaw by sending a crafted request with the 'b2s-draft-id' parameter specifying the post ID to overwrite the title and content of arbitrary posts or pages. This results in unauthorized modification of site content, compromising data integrity without affecting confidentiality or availability. The vulnerability is remotely exploitable over the network, requires authentication but no user interaction, and has a CVSS v3.1 base score of 6.5 (medium severity). No patches were linked at the time of disclosure, and no known exploits in the wild have been reported. The flaw poses a significant risk to WordPress sites using this plugin, especially those with multiple user roles and contributors.
Potential Impact
For European organizations, this vulnerability can lead to unauthorized content modification on WordPress sites using the Blog2Social plugin, potentially resulting in misinformation, defacement, or the insertion of malicious content such as phishing links or malware. This undermines the integrity of corporate communications and public-facing information, damaging brand reputation and trust. Organizations relying on WordPress for marketing, communications, or e-commerce may face operational disruptions and customer distrust. Attackers with low-level access can escalate their impact without needing higher privileges, increasing the risk from insider threats or compromised low-privilege accounts. Given the widespread use of WordPress and the popularity of social media automation plugins, the vulnerability could be leveraged in targeted campaigns against European entities, especially those with active online presence and multiple contributors. The lack of confidentiality impact reduces risk of data leakage, but the integrity compromise alone is critical for content-driven sites.
Mitigation Recommendations
1. Immediately restrict access to the Blog2Social plugin UI and AJAX endpoints to trusted user roles only, preferably administrators and editors. 2. Monitor and audit post and page modifications, especially those initiated via AJAX calls, for unusual activity or unexpected changes. 3. Disable or uninstall the Blog2Social plugin if it is not essential to reduce attack surface. 4. Apply vendor patches or updates as soon as they become available to correct the missing authorization checks. 5. Implement Web Application Firewall (WAF) rules to detect and block suspicious requests targeting the 'b2s_curation_draft' AJAX action. 6. Enforce strong authentication and account management policies to prevent unauthorized access by low-privilege users. 7. Educate content managers and administrators about this vulnerability to increase vigilance against unauthorized content changes. 8. Consider isolating critical WordPress instances or using role-based access control plugins to enforce stricter permissions beyond default WordPress capabilities.
Affected Countries
Germany, United Kingdom, France, Netherlands, Italy, Spain, Poland
CVE-2026-1942: CWE-862 Missing Authorization in pr-gateway Blog2Social: Social Media Auto Post & Scheduler
Description
The Blog2Social: Social Media Auto Post & Scheduler plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the b2s_curation_draft AJAX action in all versions up to, and including, 8.7.4. The curationDraft() function only verifies current_user_can('read') without checking whether the user has edit_post permission for the target post. Combined with the plugin granting UI access and nonce exposure to all roles, this makes it possible for authenticated attackers, with Subscriber-level access and above, to overwrite the title and content of arbitrary posts and pages by supplying a target post ID via the 'b2s-draft-id' parameter.
AI-Powered Analysis
Technical Analysis
CVE-2026-1942 is a missing authorization vulnerability (CWE-862) found in the Blog2Social: Social Media Auto Post & Scheduler WordPress plugin, affecting all versions up to 8.7.4. The vulnerability exists in the AJAX action 'b2s_curation_draft', where the curationDraft() function improperly checks user capabilities by only verifying if the user has 'read' permission rather than the more restrictive 'edit_post' permission for the targeted post. Because the plugin grants UI access and nonce exposure to all user roles, including Subscribers, an authenticated attacker with minimal privileges can exploit this flaw by sending a crafted request with the 'b2s-draft-id' parameter specifying the post ID to overwrite the title and content of arbitrary posts or pages. This results in unauthorized modification of site content, compromising data integrity without affecting confidentiality or availability. The vulnerability is remotely exploitable over the network, requires authentication but no user interaction, and has a CVSS v3.1 base score of 6.5 (medium severity). No patches were linked at the time of disclosure, and no known exploits in the wild have been reported. The flaw poses a significant risk to WordPress sites using this plugin, especially those with multiple user roles and contributors.
Potential Impact
For European organizations, this vulnerability can lead to unauthorized content modification on WordPress sites using the Blog2Social plugin, potentially resulting in misinformation, defacement, or the insertion of malicious content such as phishing links or malware. This undermines the integrity of corporate communications and public-facing information, damaging brand reputation and trust. Organizations relying on WordPress for marketing, communications, or e-commerce may face operational disruptions and customer distrust. Attackers with low-level access can escalate their impact without needing higher privileges, increasing the risk from insider threats or compromised low-privilege accounts. Given the widespread use of WordPress and the popularity of social media automation plugins, the vulnerability could be leveraged in targeted campaigns against European entities, especially those with active online presence and multiple contributors. The lack of confidentiality impact reduces risk of data leakage, but the integrity compromise alone is critical for content-driven sites.
Mitigation Recommendations
1. Immediately restrict access to the Blog2Social plugin UI and AJAX endpoints to trusted user roles only, preferably administrators and editors. 2. Monitor and audit post and page modifications, especially those initiated via AJAX calls, for unusual activity or unexpected changes. 3. Disable or uninstall the Blog2Social plugin if it is not essential to reduce attack surface. 4. Apply vendor patches or updates as soon as they become available to correct the missing authorization checks. 5. Implement Web Application Firewall (WAF) rules to detect and block suspicious requests targeting the 'b2s_curation_draft' AJAX action. 6. Enforce strong authentication and account management policies to prevent unauthorized access by low-privilege users. 7. Educate content managers and administrators about this vulnerability to increase vigilance against unauthorized content changes. 8. Consider isolating critical WordPress instances or using role-based access control plugins to enforce stricter permissions beyond default WordPress capabilities.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-02-04T21:32:56.502Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 699594d680d747be205fb502
Added to database: 2/18/2026, 10:30:46 AM
Last enriched: 2/18/2026, 10:45:07 AM
Last updated: 2/20/2026, 9:43:10 PM
Views: 19
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-27120: CWE-75: Failure to Sanitize Special Elements into a Different Plane (Special Element Injection) in vapor leaf-kit
MediumCVE-2026-27118: CWE-346: Origin Validation Error in sveltejs kit
MediumCVE-2026-27112: CWE-863: Incorrect Authorization in akuity kargo
CriticalCVE-2026-27111: CWE-862: Missing Authorization in akuity kargo
MediumCVE-2026-2857: Stack-based Buffer Overflow in D-Link DWR-M960
HighActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.