# CVE-2024-8987: Cross-site scripting in Youzify – BuddyPress Community, User Profile, Social Network & Membership Plugin for WordPress

> Authenticated attackers with contributor access can inject arbitrary scripts via the youzify_media shortcode, leading to stored XSS execution on victim pages.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/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:** 10 Oct 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-27vg-qjpq-w479

## What is CVE-2024-8987?

CVE-2024-8987 is a medium-severity cross-site scripting vulnerability in Youzify – BuddyPress Community, User Profile, Social Network & Membership Plugin for WordPress, published on 10 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Youzify – BuddyPress Community, User Profile, Social Network & Membership Plugin for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's youzify_media shortcode in all versions up to, and including, 1.3.0 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Kainelabs Youzify.

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

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

## Is CVE-2024-8987 being exploited?

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

## Other vulnerabilities in Youzify – BuddyPress Community, User Profile, Social Network & Membership Plugin for WordPress

- [CVE-2022-1950](https://insights.sbomify.com/CVE-2022-1950/): Youzify < 1.2.0 - Unauthenticated SQLi (critical 9.8)
- [CVE-2024-37494](https://insights.sbomify.com/CVE-2024-37494/): WordPress Youzify plugin <= 1.2.5 - SQL Injection vulnerability (high 8.5)
- [CVE-2024-2864](https://insights.sbomify.com/CVE-2024-2864/): WordPress Youzify - Buddypress Moderation plugin <= 1.2.5 - Unauthenticated Cross Site Scripting (XSS) vulnerability (high 7.3)
- [CVE-2024-13370](https://insights.sbomify.com/CVE-2024-13370/): Missing authorization in Youzify – BuddyPress Community, User Profile, Social Network & Membership Plugin for WordPress (medium 6.5)
- [CVE-2024-4742](https://insights.sbomify.com/CVE-2024-4742/): SQL injection in Youzify – BuddyPress Community, User Profile, Social Network & Membership Plugin for WordPress (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-8987 and fix it if it is affected.

What it is: CVE-2024-8987 is a medium-severity cross-site scripting vulnerability in Youzify – BuddyPress Community, User Profile, Social Network & Membership Plugin for WordPress, published on 10 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-8987 in the wild and no public exploit code.

Affected product: Youzify – BuddyPress Community, User Profile, Social Network & Membership Plugin for WordPress. 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-8987/ (Markdown: https://insights.sbomify.com/CVE-2024-8987/index.md)
```

## Sources

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

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