CVE-2022-3247 Blog2Social < 6.9.10 - Subscriber+ SSRF
Authenticated users can perform Server-Side Request Forgery attacks due to missing authorization and URL validation in the Blog2Social WordPress plugin.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2022-3247?
CVE-2022-3247 is a medium-severity server-side request forgery vulnerability in Unknown Blog2Social: Social Media Auto Post & Scheduler, published on 25 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
The Blog2Social: Social Media Auto Post & 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
Weakness: CWE-918
Which versions are affected by CVE-2022-3247?
It affects 1 product.
Products include Adenion Blog2social.
How do I fix CVE-2022-3247?
No fix has been published for CVE-2022-3247 yet. Limit exposure of the affected software until one is available.
Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
Is CVE-2022-3247 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3247 exists.
Other vulnerabilities in Unknown Blog2Social: Social Media Auto Post & Scheduler
- CVE-2024-3549 Blog2Social: Social Media Auto Post & Scheduler <= 7.4.1 - Authenticated (Subscriber+) SQL Injection
- CVE-2019-13572 SQL injection in n/a
- CVE-2022-3246 Blog2Social < 6.9.10 - Subscriber+ SQLi
- CVE-2021-24137 Blog2Social: Social Media Auto Post & Scheduler < 6.3.1 - Authenticated SQL Injection
- CVE-2023-40554 WordPress Blog2Social Plugin <= 7.2.0 is vulnerable to Cross Site Scripting (XSS)
Sources
Also known as GHSA-q28w-jq68-2wfw.