VYPR

Blog2social

by WordPress

Source repositories

CVEs (22)

  • CVE-2019-13572CriAug 1, 2019
    risk 0.64cvss 9.8epss 0.02

    The Adenion Blog2Social plugin through 5.5.0 for WordPress allows SQL Injection.

  • CVE-2024-3549CriJun 11, 2024
    risk 0.57cvss 9.9epss 0.01

    The Blog2Social: Social Media Auto Post & Scheduler plugin for WordPress is vulnerable to SQL Injection via the 'b2sSortPostType' parameter in all versions up to, and including, 7.4.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation…

  • CVE-2022-3246HigOct 25, 2022
    risk 0.57cvss 8.8epss 0.01

    The Blog2Social: Social Media Auto Post & Scheduler WordPress plugin before 6.9.10 does not properly sanitise and escape a parameter before using it in a SQL statement, leading to a SQL injection exploitable by any authenticated users, such as subscribers

  • CVE-2021-24137HigMar 18, 2021
    risk 0.57cvss 8.8epss 0.02

    Unvalidated input in the Blog2Social WordPress plugin, versions before 6.3.1, lead to SQL Injection in the Re-Share Posts feature, allowing authenticated users to inject arbitrary SQL commands.

  • CVE-2023-40554HigSep 6, 2023
    risk 0.46cvss 7.1epss 0.00

    Unauth. Reflected Cross-Site Scripting (XSS) vulnerability in Blog2Social, Adenion Blog2Social: Social Media Auto Post & Scheduler plugin <= 7.2.0 versions.

  • CVE-2025-5673MedJun 17, 2025
    risk 0.42cvss 6.5epss 0.00

    The Blog2Social: Social Media Auto Post & Scheduler plugin for WordPress is vulnerable to SQL Injection via the ‘prgSortPostType’ parameter in all versions up to, and including, 8.4.4 due to insufficient escaping on the user supplied parameter and lack of sufficient…

  • CVE-2022-3247MedOct 25, 2022
    risk 0.42cvss 6.5epss 0.01

    The Blog2Social: Social Media Auto Post & Scheduler WordPress plugin before 6.9.10 does not have authorisation in an AJAX action, and does not ensure that the URL to make a request to is an external one. As a result, any authenticated users, such as subscriber could perform SSRF…

  • CVE-2023-3936MedAug 21, 2023
    risk 0.40cvss 6.1epss 0.01

    The Blog2Social WordPress plugin before 7.2.1 does not sanitise and escape a parameter before outputting it back in the page, leading to a Reflected Cross-Site Scripting which could be used against high privilege users such as admin

  • CVE-2021-24956MedDec 21, 2021
    risk 0.40cvss 6.1epss 0.02

    The Blog2Social: Social Media Auto Post & Scheduler WordPress plugin before 6.8.7 does not sanitise and escape the b2sShowByDate parameter before outputting it back in an admin page, leading to a Reflected Cross-Site Scripting issue

  • CVE-2019-17550MedNov 13, 2019
    risk 0.40cvss 6.1epss 0.01

    The Blog2Social plugin before 5.9.0 for WordPress is affected by: Cross Site Scripting (XSS). The impact is: Allows an attacker to execute arbitrary HTML and JavaScript code via the b2s_id parameter. The component is: views/b2s/post.calendar.php. The attack vector is: When the…

  • CVE-2019-9576MedMar 5, 2019
    risk 0.40cvss 6.1epss 0.01

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

  • CVE-2026-7051MedMay 13, 2026
    risk 0.35cvss 5.4epss 0.00

    The Blog2Social: Social Media Auto Post & Scheduler plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 8.9.0. This is due to a missing ownership verification in the B2S_Post_Tools::deleteUserPublishPost() and…

  • CVE-2025-13558MedNov 25, 2025
    risk 0.35cvss 5.4epss 0.00

    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…

  • CVE-2024-7302MedAug 1, 2024
    risk 0.35cvss 6.4epss 0.00

    The Blog2Social: Social Media Auto Post & Scheduler plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 3gp2 file uploads in all versions up to, and including, 7.5.4 due to insufficient input sanitization and output escaping. This makes it possible for…

  • CVE-2026-4331MedMar 26, 2026
    risk 0.28cvss 4.3epss 0.00

    The Blog2Social: Social Media Auto Post & Scheduler plugin for WordPress is vulnerable to unauthorized data loss in all versions up to, and including, 8.8.2. This is due to the resetSocialMetaTags() function only verifying that the user has the 'read' capability and a valid…

  • CVE-2025-14943MedJan 10, 2026
    risk 0.28cvss 4.3epss 0.00

    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…

  • CVE-2024-3678MedApr 26, 2024
    risk 0.27cvss 5.3epss 0.01

    The Blog2Social: Social Media Auto Post & Scheduler plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 7.4.2. This makes it possible for unauthenticated attackers to view limited information from password protected posts.

  • CVE-2022-3622MedOct 20, 2023
    risk 0.27cvss 4.1epss 0.01

    The Blog2Social plugin for WordPress is vulnerable to authorization bypass due to missing capability checks in versions up to, and including, 6.9.11. This makes it possible for authenticated attackers, with subscriber-level permissions and above, to change some plugin settings…

  • CVE-2026-4330MedApr 8, 2026
    risk 0.21cvss 4.3epss 0.01

    The Blog2Social: Social Media Auto Post & Scheduler plugin for WordPress is vulnerable to authorization bypass through user-controlled key in all versions up to, and including, 8.8.3. This is due to the plugin's AJAX handlers failing to validate that the user-supplied 'b2s_id'…

  • CVE-2025-12560MedNov 6, 2025
    risk 0.21cvss 4.3epss 0.00

    The Blog2Social: Social Media Auto Post & Scheduler plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 8.6.0 via the getFullContent() function. This makes it possible for authenticated attackers, with Subscriber-level access…

Page 1 of 2