BuddyPress XProfile Image Field: Unauthenticated Arbitrary File Deletion
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- None · High · High
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA.
Summary
The BuddyPress XProfile Custom Image Field plugin for WordPress is vulnerable to arbitrary file deletion in all versions from 0 through 3.1.0. The bpxp_image_field_update_on_user_activation() function calls unlink() on a path built from visitor-supplied signup metadata without checking that the path stays inside the profile image directory, which is an improper limitation of a pathname to a restricted directory (CWE-22). An unauthenticated attacker can delete arbitrary files on the server during registration, which can lead to remote code execution when a file such as wp-config.php is deleted. Exploitation requires open registration and an image-type profile field on the signup form.
Written with Claude Haiku 5.5 from the sources below · 2026-11-07
Description from the CNA
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
The sources list no fixed version for BuddyPress XProfile Custom Image Field.
Written with Claude Haiku 5.5 from the sources below · 2026-11-07
Timeline
- 2026-11-03 Threatist record created from CVE-2026-120518
- 2026-11-03 Alias added: GHSA-cjfm-vrh6-rjxq
- 2026-11-07 CISA SSVC decision points changed
References
Other 7
- https://www.wordfence.com/threat-intel/vulnerabilities/id/1a53bcf5-61ed-427c-9efd-29c9309d2426?source=cve
- https://plugins.trac.wordpress.org/browser/buddypress-xprofile-image-field/tags/3.1.0/bp-xprofile-image-field.php#L526
- https://plugins.trac.wordpress.org/browser/buddypress-xprofile-image-field/tags/3.1.0/bp-xprofile-image-field.php#L488
- https://plugins.trac.wordpress.org/browser/buddypress-xprofile-image-field/tags/3.1.0/bp-xprofile-image-field.php#L494
- https://plugins.trac.wordpress.org/browser/buddypress-xprofile-image-field/tags/3.1.0/bp-xprofile-image-field.php#L507
- https://plugins.trac.wordpress.org/browser/buddypress-xprofile-image-field/tags/3.1.0/bp-xprofile-image-field.php#L587
- https://nvd.nist.gov/vuln/detail/CVE-2025-48158
Sources
- CVE-2026-120518 · CVE Program
- CVE-2026-120518 · NVD
- FIRST EPSS
- GHSA-cjfm-vrh6-rjxq · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences