{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-3622 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-3622 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-3622 is a medium-severity missing authorization vulnerability in pr-gateway Blog2Social: Social Media Auto Post \u0026 Scheduler, published on 20 Oct 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-3622 and fix it if it is affected.\n\nWhat it is: CVE-2022-3622 is a medium-severity missing authorization vulnerability in pr-gateway Blog2Social: Social Media Auto Post \u0026 Scheduler, published on 20 Oct 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-3622 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-2022-3622/ (Markdown: https://insights.sbomify.com/CVE-2022-3622/index.md)","id":"CVE-2022-3622","markdown":"https://insights.sbomify.com/CVE-2022-3622/index.md","name":"CVE-2022-3622","record":{"aliases":["GHSA-2wq9-hq2m-2hfq"],"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 modify admin-only plugin settings due to missing capability checks in Blog2Social.","user_interaction":"required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"blog2social","vendor":"adenion"}],"cvss":{"score":4.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"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 intended to be modifiable by admins only.","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":"Blog2Social \u003c= 6.9.11 - Missing Authorization to Authenticated (Subscriber+) Settings Update","id":"CVE-2022-3622","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2022"},"n_packages":0,"n_references":4,"next":{"headline":"Linux Kernel BPF gup.c follow_page_pte race condition","id":"CVE-2022-3623"},"packages":[],"prev":{"headline":"Linux Kernel nilfs2 inode.c nilfs_bmap_lookup_at_level null pointer dereference","id":"CVE-2022-3621"},"products":["Blog2Social: Social Media Auto Post \u0026 Scheduler"],"published":"2023-10-20","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.5,"headline":"Blog2Social \u003c 6.9.10 - Subscriber+ SSRF","id":"CVE-2022-3247","kev_date_added":null,"published":"2022-10-25"},{"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["pr-gateway"]},"summary":"Authenticated subscribers can modify admin-only plugin settings due to missing capability checks in Blog2Social.","url":"https://insights.sbomify.com/CVE-2022-3622/"}