{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3247 exists.","fix":"No fix has been published for CVE-2022-3247 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-3247 is a medium-severity server-side request forgery vulnerability in Unknown Blog2Social: Social Media Auto Post \u0026 Scheduler, published on 25 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-3247 and fix it if it is affected.\n\nWhat it is: CVE-2022-3247 is a medium-severity server-side request forgery vulnerability in Unknown Blog2Social: Social Media Auto Post \u0026 Scheduler, published on 25 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3247 exists.\n\nAffected product: Unknown 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-2022-3247/ (Markdown: https://insights.sbomify.com/CVE-2022-3247/index.md)","id":"CVE-2022-3247","markdown":"https://insights.sbomify.com/CVE-2022-3247/index.md","name":"CVE-2022-3247","record":{"aliases":["GHSA-q28w-jq68-2wfw"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated users can perform Server-Side Request Forgery attacks due to missing authorization and URL validation in the Blog2Social WordPress plugin.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"blog2social","vendor":"adenion"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"The Blog2Social: Social Media Auto Post \u0026 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 attacks","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Blog2Social \u003c 6.9.10 - Subscriber+ SSRF","id":"CVE-2022-3247","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Openshift api admission checks does not enforce \"custom-host\" permissions","id":"CVE-2022-3248"},"packages":[],"prev":{"headline":"Blog2Social \u003c 6.9.10 - Subscriber+ SQLi","id":"CVE-2022-3246"},"products":["Blog2Social: Social Media Auto Post \u0026 Scheduler"],"published":"2022-10-25","related":[{"cvss_score":9.9,"headline":"Blog2Social: Social Media Auto Post \u0026 Scheduler \u003c= 7.4.1 - Authenticated (Subscriber+) SQL Injection","id":"CVE-2024-3549","kev_date_added":null,"published":"2024-06-11"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2019-13572","kev_date_added":null,"published":"2019-08-01"},{"cvss_score":8.8,"headline":"Blog2Social \u003c 6.9.10 - Subscriber+ SQLi","id":"CVE-2022-3246","kev_date_added":null,"published":"2022-10-25"},{"cvss_score":8.8,"headline":"Blog2Social: Social Media Auto Post \u0026 Scheduler \u003c 6.3.1 - Authenticated SQL Injection","id":"CVE-2021-24137","kev_date_added":null,"published":"2021-03-18"},{"cvss_score":7.1,"headline":"WordPress Blog2Social Plugin \u003c= 7.2.0 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-40554","kev_date_added":null,"published":"2023-09-06"},{"cvss_score":6.4,"headline":"Cross-site scripting in Blog2Social: Social Media Auto Post \u0026 Scheduler","id":"CVE-2024-7302","kev_date_added":null,"published":"2024-08-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-05-09","vendors":["Unknown"]},"summary":"Authenticated users can perform Server-Side Request Forgery attacks due to missing authorization and URL validation in the Blog2Social WordPress plugin.","url":"https://insights.sbomify.com/CVE-2022-3247/"}