{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-12560 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-12560 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-12560 is a medium-severity server-side request forgery vulnerability in pr-gateway Blog2Social: Social Media Auto Post \u0026 Scheduler, published on 6 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-12560 and fix it if it is affected.\n\nWhat it is: CVE-2025-12560 is a medium-severity server-side request forgery vulnerability in pr-gateway Blog2Social: Social Media Auto Post \u0026 Scheduler, published on 6 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-12560 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-2025-12560/ (Markdown: https://insights.sbomify.com/CVE-2025-12560/index.md)","id":"CVE-2025-12560","markdown":"https://insights.sbomify.com/CVE-2025-12560/index.md","name":"CVE-2025-12560","record":{"aliases":["GHSA-rqm6-jmg2-pgr4"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated subscribers can exploit a blind SSRF vulnerability in the Blog2Social WordPress plugin to query and modify internal services.","user_interaction":"not_required","vuln_class":"ssrf"},"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-918","name":"Server-Side Request Forgery"}],"description":"The Blog2Social: Social Media Auto Post \u0026 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 and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.","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":"Server-side request forgery in Blog2Social: Social Media Auto Post \u0026 Scheduler","id":"CVE-2025-12560","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2025-12561"},"packages":[],"prev":{"headline":"Information Disclosure in Common Teams API","id":"CVE-2025-12559"},"products":["Blog2Social: Social Media Auto Post \u0026 Scheduler"],"published":"2025-11-06","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["pr-gateway"]},"summary":"Authenticated subscribers can exploit a blind SSRF vulnerability in the Blog2Social WordPress plugin to query and modify internal services.","url":"https://insights.sbomify.com/CVE-2025-12560/"}