# CVE-2024-3678: Blog2Social: Social Media Auto Post & Scheduler <= 7.4.2 - Information Exposure

> Unauthenticated attackers can view limited information from password-protected posts in the Blog2Social WordPress plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Apr 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-hqqq-4jv4-jmj5

## What is CVE-2024-3678?

CVE-2024-3678 is a medium-severity vulnerability in pr-gateway Blog2Social: Social Media Auto Post & Scheduler, published on 26 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Blog2Social: Social Media Auto Post & Scheduler plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 7.4.2. This makes it possible for unauthenticated attackers to view limited information from password protected posts.

Weakness: CWE-922 (Insecure Storage of Sensitive Information), CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2024-3678?

It affects 1 product.


Products: Adenion Blog2social.

## How do I fix CVE-2024-3678?

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

## Is CVE-2024-3678 being exploited?

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

## Other vulnerabilities in pr-gateway 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-2024-3678 and fix it if it is affected.

What it is: CVE-2024-3678 is a medium-severity vulnerability in pr-gateway Blog2Social: Social Media Auto Post & Scheduler, published on 26 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-3678 in the wild and no public exploit code.

Affected product: pr-gateway 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-2024-3678/ (Markdown: https://insights.sbomify.com/CVE-2024-3678/index.md)
```

## Sources

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

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