XProfile Image Fieldに未認証でファイル削除の脆弱性
Summary
BuddyPress向けのWordPressプラグインXProfile Image Fieldに、サーバー上の任意のファイルを消せる脆弱性が公表されました。会員登録を公開しているサイトは版を確認し、配布元の告知で修正版を調べてください。
AI summary
Produced by SecPulse using an external AI model; it may contain mistakes. Check the original description and references below before acting on it.
BuddyPress向けのWordPressプラグインXProfile Image Fieldに、サーバー上の任意のファイルを消せる脆弱性が公表されました。会員登録を公開しているサイトは版を確認し、配布元の告知で修正版を調べてください。
Affected packages
| Ecosystem | Package | Affected | Fixed |
|---|---|---|---|
| kalengi | BuddyPress XProfile Custom Image Field |
≤ 3.1.0 |
— |
Original description The description as published by the source.
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.
Source: CVE.org (CVE Program・cvelistV5) NVD GitHub Advisory