# 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.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Oct 2022
- **Updated:** 9 May 2025
- **Also known as:** GHSA-q28w-jq68-2wfw

## 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 (Server-Side Request Forgery)

## Which versions are affected by CVE-2022-3247?

It affects 1 product.


Products: 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.

## 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](https://insights.sbomify.com/CVE-2024-3549/): Blog2Social: Social Media Auto Post & Scheduler <= 7.4.1 - Authenticated (Subscriber+) SQL Injection (critical 9.9)
- [CVE-2019-13572](https://insights.sbomify.com/CVE-2019-13572/): SQL injection in n/a (critical 9.8)
- [CVE-2022-3246](https://insights.sbomify.com/CVE-2022-3246/): Blog2Social < 6.9.10 - Subscriber+ SQLi (high 8.8)
- [CVE-2021-24137](https://insights.sbomify.com/CVE-2021-24137/): Blog2Social: Social Media Auto Post & Scheduler < 6.3.1 - Authenticated SQL Injection (high 8.8)
- [CVE-2023-40554](https://insights.sbomify.com/CVE-2023-40554/): WordPress Blog2Social Plugin <= 7.2.0 is vulnerable to Cross Site Scripting (XSS) (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-3247 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3247 exists.

Affected product: Unknown Blog2Social: Social Media Auto Post & Scheduler. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-3247/ (Markdown: https://insights.sbomify.com/CVE-2022-3247/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-3247
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-3247
- OSV: https://osv.dev/vulnerability/CVE-2022-3247

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-3247/
Summaries are generated and may contain mistakes; the official description above is the record.