{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-4331 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-4331 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-4331 is a medium-severity missing authorization vulnerability in pr-gateway Blog2Social: Social Media Auto Post \u0026 Scheduler, published on 26 Mar 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-4331 and fix it if it is affected.\n\nWhat it is: CVE-2026-4331 is a medium-severity missing authorization vulnerability in pr-gateway Blog2Social: Social Media Auto Post \u0026 Scheduler, published on 26 Mar 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-4331 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-4331/ (Markdown: https://insights.sbomify.com/CVE-2026-4331/index.md)","id":"CVE-2026-4331","markdown":"https://insights.sbomify.com/CVE-2026-4331/index.md","name":"CVE-2026-4331","record":{"aliases":["GHSA-x2p4-4cw9-m5ch"],"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 subscribers can delete all social media meta tags for every post due to insufficient authorization checks 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":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","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 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 b2s_security_nonce, both of which are available to Subscriber-level users, as the plugin grants 'blog2social_access' capability to all roles upon activation, allowing them to access the plugin's admin pages where the nonce is output. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete all _b2s_post_meta records from the wp_postmeta table, permanently removing all custom social media meta tags for every post on the site.","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-4331","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":10,"next":{"headline":"Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in GitLab","id":"CVE-2026-4332"},"packages":[],"prev":{"headline":"Missing authorization in Blog2Social: Social Media Auto Post \u0026 Scheduler","id":"CVE-2026-4330"},"products":["Blog2Social: Social Media Auto Post \u0026 Scheduler"],"published":"2026-03-26","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-04-08","vendors":["pr-gateway"]},"summary":"Authenticated subscribers can delete all social media meta tags for every post due to insufficient authorization checks in the Blog2Social WordPress plugin.","url":"https://insights.sbomify.com/CVE-2026-4331/"}