# CVE-2021-24137: Blog2Social: Social Media Auto Post & Scheduler < 6.3.1 - Authenticated SQL Injection

> Authenticated attackers can inject arbitrary SQL commands via the Re-Share Posts feature in the Blog2Social WordPress plugin.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 18 Mar 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-fxmq-6v3w-26hj

## What is CVE-2021-24137?

CVE-2021-24137 is a high-severity SQL injection vulnerability in Unknown Blog2Social: Social Media Auto Post & Scheduler, published on 18 Mar 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unvalidated input in the Blog2Social WordPress plugin, versions before 6.3.1, lead to SQL Injection in the Re-Share Posts feature, allowing authenticated users to inject arbitrary SQL commands.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2021-24137?

It affects 1 product.


Products: Adenion Blog2social.

## How do I fix CVE-2021-24137?

No fix has been published for CVE-2021-24137 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-24137 being exploited?

There is no known exploitation of CVE-2021-24137 in the wild and no public exploit code.

## 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-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)
- [CVE-2022-3247](https://insights.sbomify.com/CVE-2022-3247/): Blog2Social < 6.9.10 - Subscriber+ SSRF (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-24137 and fix it if it is affected.

What it is: CVE-2021-24137 is a high-severity SQL injection vulnerability in Unknown Blog2Social: Social Media Auto Post & Scheduler, published on 18 Mar 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-24137 in the wild and no public exploit code.

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-2021-24137/ (Markdown: https://insights.sbomify.com/CVE-2021-24137/index.md)
```

## Sources

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

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