{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-7051 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-7051 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-7051 is a medium-severity missing authorization vulnerability in pr-gateway Blog2Social: Social Media Auto Post \u0026 Scheduler, published on 13 May 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-7051 and fix it if it is affected.\n\nWhat it is: CVE-2026-7051 is a medium-severity missing authorization vulnerability in pr-gateway Blog2Social: Social Media Auto Post \u0026 Scheduler, published on 13 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-7051 in the wild and no public exploit code.\n\nAffected product: pr-gateway Blog2Social: Social Media Auto Post \u0026 Scheduler. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-7051/ (Markdown: https://insights.sbomify.com/CVE-2026-7051/index.md)","id":"CVE-2026-7051","markdown":"https://insights.sbomify.com/CVE-2026-7051/index.md","name":"CVE-2026-7051","record":{"aliases":[],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated attackers can delete arbitrary social media post records of other users due to missing ownership verification in the Blog2Social WordPress plugin.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"The Blog2Social: Social Media Auto Post \u0026 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 B2S_Post_Tools::deleteUserSchedPost() functions, neither function includes a blog_user_id constraint in its database query, allowing authenticated attackers to soft-delete any user's B2S post records by supplying arbitrary sequential wp_b2s_posts.id values via the 'postId' parameter. This makes it possible for authenticated attackers to delete other users' published and scheduled social media post records, disrupting content publishing workflows.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Missing authorization in Blog2Social: Social Media Auto Post \u0026 Scheduler","id":"CVE-2026-7051","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":14,"next":{"headline":"HT Contact Form \u003c= 2.8.2 - Unauthenticated Stored Cross-Site Scripting via File Upload Field","id":"CVE-2026-7052"},"packages":[],"prev":{"headline":"Missing authorization in Forms Rb","id":"CVE-2026-7050"},"products":["Blog2Social: Social Media Auto Post \u0026 Scheduler"],"published":"2026-05-13","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-13","vendors":["pr-gateway"]},"summary":"Authenticated attackers can delete arbitrary social media post records of other users due to missing ownership verification in the Blog2Social WordPress plugin.","url":"https://insights.sbomify.com/CVE-2026-7051/"}