# CVE-2021-24443: Youzify < 1.0.7 - Stored Cross-Site Scripting via Biography

> Authenticated users can inject scripts into the biography field, potentially allowing attackers to hijack admin accounts by tricking them into viewing the profile.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Aug 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-w5vh-q269-m424

## What is CVE-2021-24443?

CVE-2021-24443 is a medium-severity cross-site scripting vulnerability in Unknown Youzify – BuddyPress Community, User Profile, Social Network & Membership Plugin for WordPress, published on 2 Aug 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The About Me widget of the Youzify – BuddyPress Community, User Profile, Social Network & Membership WordPress plugin before 1.0.7 does not properly sanitise its Biography field, allowing any authenticated user to set Cross-Site Scripting payloads in it, which will be executed when viewing the affected user profile. This could allow a low privilege user to gain unauthorised access to the admin side of the blog by targeting an admin, inducing them to view their profile with a malicious payload adding a rogue account for example.

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

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

It affects 1 product.


Products: Kainelabs Youzify.

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

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

## Is CVE-2021-24443 being exploited?

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

## Other vulnerabilities in Unknown 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-2021-24443 and fix it if it is affected.

What it is: CVE-2021-24443 is a medium-severity cross-site scripting vulnerability in Unknown Youzify – BuddyPress Community, User Profile, Social Network & Membership Plugin for WordPress, published on 2 Aug 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-24443 in the wild and no public exploit code.

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

## Sources

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

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