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-13558: CWE-862 Missing Authorization in pr-gateway Blog2Social: Social Media Auto Post & Scheduler

0
Medium
VulnerabilityCVE-2025-13558cvecve-2025-13558cwe-862
Published: Tue Nov 25 2025 (11/25/2025, 04:37:59 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 unauthorized modification of data due to a missing capability check on the 'deleteUserCcDraftPost' function in all versions up to, and including, 8.7.0. This makes it possible for authenticated attackers, with Subscriber-level access and above, to change the status of arbitrary posts to trash.

AI-Powered Analysis

AILast updated: 11/25/2025, 05:06:28 UTC

Technical Analysis

CVE-2025-13558 is a vulnerability classified under CWE-862 (Missing Authorization) found in the Blog2Social: Social Media Auto Post & Scheduler plugin for WordPress, versions up to and including 8.7.0. The root cause is the absence of a capability check in the 'deleteUserCcDraftPost' function, which is responsible for managing draft posts. This flaw permits any authenticated user with at least Subscriber-level privileges to alter the status of arbitrary posts, specifically to move them to the trash, without proper authorization. Since Subscriber-level access is commonly granted to users with minimal privileges, this vulnerability significantly lowers the barrier for exploitation. The attack vector is remote over the network (AV:N), requires low attack complexity (AC:L), and only low privileges (PR:L), with no user interaction needed (UI:N). The impact affects integrity (I:L) and availability (A:L) but not confidentiality. Exploiting this vulnerability could disrupt content workflows, cause unintended data deletion, or facilitate further attacks by manipulating post statuses. Although no public exploits are known yet, the widespread use of WordPress and this plugin increases the risk. The vulnerability was published on November 25, 2025, with a CVSS v3.1 score of 5.4, indicating medium severity. No patches were listed at the time of reporting, so mitigation must rely on access controls and monitoring until fixes are released.

Potential Impact

For European organizations, this vulnerability poses a moderate risk primarily to the integrity and availability of web content managed via WordPress sites using the Blog2Social plugin. Unauthorized users with minimal privileges can trash posts, potentially leading to data loss, disruption of scheduled social media posts, and damage to brand reputation. Organizations relying heavily on automated social media posting for marketing or communications could experience operational interruptions. Additionally, attackers could leverage this vulnerability as a foothold to escalate privileges or conduct further attacks within the WordPress environment. The impact is especially critical for sectors with high digital presence such as media, e-commerce, and public services. Given the ease of exploitation and the commonality of WordPress deployments in Europe, the vulnerability could be exploited at scale if unpatched. However, the lack of known exploits in the wild and the requirement for authenticated access somewhat limit immediate widespread impact.

Mitigation Recommendations

1. Immediately restrict user roles and permissions to the minimum necessary, particularly limiting Subscriber-level users from accessing post management functions where possible. 2. Monitor WordPress logs and audit trails for unusual post status changes, especially posts being moved to trash by low-privilege users. 3. Implement web application firewalls (WAF) with custom rules to detect and block suspicious requests targeting the 'deleteUserCcDraftPost' function or related endpoints. 4. Until an official patch is released, consider disabling or removing the Blog2Social plugin if feasible, or replacing it with alternative plugins that do not exhibit this vulnerability. 5. Educate site administrators and content managers about the risk and encourage regular backups of WordPress content to enable quick recovery. 6. Keep WordPress core and all plugins updated, and subscribe to vendor security advisories for prompt patch application once available. 7. Employ multi-factor authentication (MFA) to reduce the risk of compromised accounts being used to exploit this vulnerability.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-11-22T15:46:48.214Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6925392a441560fe7ee067e3

Added to database: 11/25/2025, 5:05:46 AM

Last enriched: 11/25/2025, 5:06:28 AM

Last updated: 11/25/2025, 7:53:55 AM

Views: 4

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 enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats