# CVE-2023-28694: Cross-site request forgery in Wbcom Designs – BuddyPress Activity Social Share

> Attackers can trick users into performing unintended actions in the BuddyPress Activity Social Share plugin, potentially modifying activity data.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L`)
- **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:** 12 Nov 2023
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-94x4-p49x-fp3r

## What is CVE-2023-28694?

CVE-2023-28694 is a medium-severity vulnerability in Wbcom Designs – BuddyPress Activity Social Share, published on 12 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Cross-Site Request Forgery (CSRF) vulnerability in Wbcom Designs Wbcom Designs – BuddyPress Activity Social Share plugin <= 3.5.0 versions.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2023-28694?

It affects 1 product.


Products: Wbcomdesigns Buddypress Activity Social Share.

## How do I fix CVE-2023-28694?

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

## Is CVE-2023-28694 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-28694 and fix it if it is affected.

What it is: CVE-2023-28694 is a medium-severity vulnerability in Wbcom Designs – BuddyPress Activity Social Share, published on 12 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-28694 in the wild and no public exploit code.

Affected product: Wbcom Designs – BuddyPress Activity Social Share. 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-2023-28694/ (Markdown: https://insights.sbomify.com/CVE-2023-28694/index.md)
```

## Sources

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

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