Is BuddyPress XProfile Custom Image Field safe to use?

Laskyr does not give safety verdicts. BuddyPress XProfile Custom Image Field is closed on wordpress.org. Closed on 2026-10-05. Closed plugins get no updates through WordPress, so new security holes will not be fixed for you. Keep BuddyPress XProfile Custom Image Field on the latest version and remove it if you do not use it.

Which versions of BuddyPress XProfile Custom Image Field are vulnerable?

Known issues on record (newest first): Arbitrary file deletion (3.1.0 and older); Path traversal / file read (3.0.1 and older, fixed in 3.1.0). The full list with sources is on this page.

What should I do if my BuddyPress XProfile Custom Image Field is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update buddypress-xprofile-image-field). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · buddypress-xprofile-image-field · data as of 2026-11-04

Is BuddyPress XProfile Custom Image Field safe? Known vulnerabilities and latest version

Status: Closed 2026-10-05
Known issues on record: 2
Unpatched in latest: 0

What to do

Replace it. A closed plugin gets no updates through WordPress, so any hole found from now on stays open.
Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deleting removes its files; deactivating alone leaves them on the server.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.

With WP-CLI, once you have a replacement: wp plugin deactivate buddypress-xprofile-image-field && wp plugin delete buddypress-xprofile-image-field

Check your version

Known vulnerabilities

2 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version. 2 record(s) do not state which versions are affected.

critical 9.1 CVE-2026-120518 · published 2026-11-03

Arbitrary file deletion in BuddyPress XProfile Custom Image Field (3.1.0 and older)

Affected: 3.1.0 and older
Fixed in: unknown
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

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.

NVD CVE-2026-120518 Wordfence advisory nvd.nist.gov Plugin source

high 8.6 CVE-2025-48158 · published 2025-08-20

Path traversal / file read in BuddyPress XProfile Custom Image Field (3.0.1 and older)

Affected: 3.0.1 and older
Fixed in: 3.1.0
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Alex Githatu BuddyPress XProfile Custom Image Field buddypress-xprofile-image-field allows Path Traversal.This issue affects BuddyPress XProfile Custom Image Field: from n/a through <= 3.0.1.

NVD CVE-2025-48158 Patchstack advisory

Recent activity

2026-10-05 — closed on wordpress.org.
2026-11-03 — Arbitrary file deletion disclosed (CVE-2026-120518), fix version not stated.
2025-08-20 — Path traversal / file read disclosed (CVE-2025-48158), fixed in 3.1.0.

Free. We check the CVE feeds every day and email you only when a new issue for BuddyPress XProfile Custom Image Field (buddypress-xprofile-image-field) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Arbitrary file deletion (1) · Path traversal and file read (1)

Where this data comes from

Version, last update, installs, closure: wordpress.org/plugins/buddypress-xprofile-image-field (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/buddypress-xprofile-image-field"><img src="https://laskyr.com/plugins/buddypress-xprofile-image-field/badge.svg" alt="BuddyPress XProfile Custom Image Field vulnerability status"></a>

← Check another plugin · Free hacked-site scan