Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-14943: CWE-863 Incorrect Authorization in pr-gateway Blog2Social: Social Media Auto Post & Scheduler

0
Medium
VulnerabilityCVE-2025-14943cvecve-2025-14943cwe-863
Published: Sat Jan 10 2026 (01/10/2026, 06:32:34 UTC)
Source: CVE Database V5
Vendor/Project: pr-gateway
Product: Blog2Social: Social Media Auto Post & Scheduler

Description

The Blog2Social: Social Media Auto Post & Scheduler plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 8.7.2. This is due to a misconfigured authorization check on the 'getShipItemFullText' function which only verifies that a user has the 'read' capability (Subscriber-level) and a valid nonce, but fails to verify whether the user has permission to access the specific post being requested. This makes it possible for authenticated attackers, with Subscriber-level access and above, to extract data from password-protected, private, or draft posts.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/27/2026, 11:44:54 UTC

Technical Analysis

CVE-2025-14943 is a vulnerability classified under CWE-863 (Incorrect Authorization) affecting all versions up to and including 8.7.2 of the Blog2Social: Social Media Auto Post & Scheduler plugin for WordPress. The root cause is a misconfigured authorization check in the 'getShipItemFullText' function. This function validates that a user has the 'read' capability (which includes Subscriber-level users) and a valid nonce but fails to verify whether the user has permission to access the specific post requested. Consequently, authenticated users with minimal privileges can retrieve the full text of posts that are password-protected, private, or in draft status, which should normally be inaccessible to them. The vulnerability is exploitable remotely without user interaction, leveraging the WordPress authentication system. The CVSS v3.1 score is 4.3 (medium severity), reflecting low complexity and no user interaction required, but limited impact confined to confidentiality. No patches or fixes are currently linked, and no known exploits have been observed in the wild. This vulnerability highlights a common authorization logic flaw where capability checks are insufficiently granular, allowing privilege escalation in data access within WordPress plugins.

Potential Impact

The primary impact of CVE-2025-14943 is the unauthorized disclosure of sensitive content stored in password-protected, private, or draft posts within WordPress sites using the vulnerable Blog2Social plugin. Organizations relying on this plugin risk exposure of confidential or proprietary information to any authenticated user with Subscriber-level access or higher, including potentially low-privileged users or compromised accounts. This can lead to information leakage, loss of privacy, and reputational damage. While the vulnerability does not affect data integrity or availability, the breach of confidentiality can be significant, especially for businesses or individuals managing sensitive social media content or internal communications. The ease of exploitation and the widespread use of WordPress and this plugin increase the risk of targeted attacks or insider threats leveraging this flaw. Without remediation, attackers can systematically extract protected content, undermining trust in the affected platforms.

Mitigation Recommendations

To mitigate CVE-2025-14943, organizations should immediately restrict access to the Blog2Social plugin by limiting Subscriber-level user capabilities or disabling the plugin if not essential. Administrators should monitor and audit user roles and permissions to ensure minimal necessary access. Applying principle of least privilege to user accounts reduces the risk of exploitation. Since no official patch is currently available, consider implementing custom authorization checks or filters in WordPress to enforce post-level access control on the 'getShipItemFullText' function. Additionally, temporarily removing or restricting access to sensitive posts (e.g., changing their status or visibility) can reduce exposure. Monitoring logs for unusual access patterns to private or draft posts can help detect exploitation attempts. Stay updated with vendor advisories for forthcoming patches and apply them promptly once released. Employing Web Application Firewalls (WAFs) with rules to detect anomalous API calls related to this function may also help mitigate risk.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-12-18T23:57:47.575Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6961f7c0c540fa4b54565839

Added to database: 1/10/2026, 6:54:56 AM

Last enriched: 2/27/2026, 11:44:54 AM

Last updated: 3/26/2026, 9:20:04 AM

Views: 108

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses