PatchSiren cyber security CVE debrief
CVE-2026-92829 pr-gateway CVE debrief
The Blog2Social: Social Media Auto Post & Scheduler plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 9.1.0. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with contributor-level access and above, to view, modify, or delete other users' Blog2Social records, including disclosing another user's network authentication IDs and scheduled post content, overwriting Open Graph and Twitter Card post metadata on posts they do not own, rebinding another user's social-network authorization, and mass-hiding all users' scheduled posts sitewide.
- Vendor
- pr-gateway
- Product
- Blog2Social: Social Media Auto Post & Scheduler
- CVSS
- MEDIUM 4.3
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-25
- Original CVE updated
- 2026-09-25
- Advisory published
- 2026-09-25
- Advisory updated
- 2026-09-25
Who should care
Defenders responsible for WordPress installations with the Blog2Social plugin should assess exposure to authenticated attackers with contributor-level access and above, and prioritize verifying the impact of potential unauthorized access to Blog2Social records.
Why it matters
The Blog2Social authorization bypass vulnerability allows authenticated attackers to access and modify sensitive information, posing a risk to WordPress installations with contributor-level access and above.
- Potential unauthorized access to Blog2Social records
- Disclosure of sensitive information, such as network authentication IDs and scheduled post content
- Modification of post metadata, including Open Graph and Twitter Card information
- Rebinding of social-network authorization
Technical summary
The Blog2Social plugin for WordPress is vulnerable to authorization bypass due to improper verification of user authorization. This allows authenticated attackers with contributor-level access and above to view, modify, or delete other users' Blog2Social records, including disclosing another user's network authentication IDs and scheduled post content, overwriting Open Graph and Twitter Card post metadata on posts they do not own, rebinding another user's social-network authorization, and mass-hiding all users' scheduled posts sitewide. The plugin's b2s_security_nonce is emitted on the post-edit meta box, which Contributors can render, making the nonce available to any authenticated user at that role level or
Defensive priority
Defenders should prioritize verifying exposure of Blog2Social installations to authenticated attackers with contributor-level access and above, and assess the impact of potential unauthorized access to Blog2Social records.
Recommended defensive actions
- Verify exposure of Blog2Social installations to authenticated attackers with contributor-level access and above
- Assess the impact of potential unauthorized access to Blog2Social records
- Restrict access to Blog2Social records to authorized users only
- Monitor for suspicious activity related to Blog2Social records
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
Evidence notes
The CVE record and NVD entry provide details on the vulnerability, including its description, CVSS score, and references to source code. The Blog2Social plugin for WordPress is vulnerable to authorization bypass due to improper verification of user authorization. This allows authenticated attackers with contributor-level access and above to view, modify, or delete other users' Blog2Social records. The vulnerability has a CVSS score of 4.3 and is considered MEDIUM severity. The plugin's b2s_security_nonce is emitted on the post-edit
Sources and references
Verified primary and authoritative sources
-
CVE-2026-92829 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-92829
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-92829 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-92829
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://plugins.trac.wordpress.org/browser/blog2social/tags/9.1.0/includes/Ajax/Get.php
-
Source reference
Unverified legacy reference
URL: https://plugins.trac.wordpress.org/browser/blog2social/tags/9.1.0/includes/Ajax/Post.php
-
Source reference
Unverified legacy reference
URL: https://plugins.trac.wordpress.org/browser/blog2social/tags/9.1.0/includes/B2S/Calendar/Filter.php
-
Source reference
Unverified legacy reference
URL: https://plugins.trac.wordpress.org/browser/blog2social/tags/9.1.0/includes/B2S/Post/Tools.php
-
Source reference
Unverified legacy reference
URL: https://plugins.trac.wordpress.org/browser/blog2social/tags/9.1.1/includes/Ajax/Post.php
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.