# CVE-2026-120518: The BuddyPress XProfile Image Field plugin for WordPress is vulnerable to arbitrary file deletion in all versions up to, and including, 3.1.0.


- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 3 Nov 2026
- **Updated:** 7 Nov 2026
- **Also known as:** GHSA-cjfm-vrh6-rjxq

## What is CVE-2026-120518?

CVE-2026-120518 is a critical vulnerability in kalengi BuddyPress XProfile Custom Image Field, published on 3 Nov 2026. 

### Official description

The BuddyPress XProfile Image Field plugin for WordPress is vulnerable to arbitrary file deletion in all versions up to, and including, 3.1.0. This is due to bpxp_image_field_update_on_user_activation() calling unlink() on a path built from visitor-supplied signup metadata with no realpath() resolution, no containment check against the profile-image directory and no extension allow-list. Submitting a zero-byte file with the 'field_N_hidden' parameter during registration makes the plugin store the raw value, which is then resolved against the document root when the pending signup is activated. This makes it possible for unauthenticated attackers to delete arbitrary files on the server, which can easily lead to remote code execution when the right file (such as wp-config.php) is deleted. Requires open registration and an image-type profile field on the signup form.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-120518?


## How do I fix CVE-2026-120518?

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

## Is CVE-2026-120518 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120518 and fix it if it is affected.

What it is: CVE-2026-120518 is a critical vulnerability in kalengi BuddyPress XProfile Custom Image Field, published on 3 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120518 in the wild and no public exploit code.

Affected product: kalengi BuddyPress XProfile Custom Image Field. 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-2026-120518/ (Markdown: https://insights.sbomify.com/CVE-2026-120518/index.md)
```

## Sources

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

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