Skip to main content
VulnerabilityPublished

CVE-2026-120518: BuddyPress XProfile Custom Image Field (WordPress plugin) · Path Traversal

Affects BuddyPress XProfile Custom Image Field (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.1 Critical.

Data as of 3 Nov 2026, 05:13 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.19.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
kalengiBuddyPress XProfile Custom Image FieldAffected
  • <=3.1.0
Fixed in–

AI-suggested

Users should disable open registration or remove the image-type profile field from the signup form to prevent exploitation. Monitor vendor advisories for an official fix. Until a patch is available, restrict access to the signup process and consider applying custom code to validate and sanitize file paths before unlinking.

Description

The BuddyPress XProfile Image Field plugin for WordPress versions up to 3.1.0 contains a critical path traversal vulnerability allowing unauthenticated attackers to delete arbitrary files on the server. This occurs because the plugin calls unlink() on a path derived from user-supplied signup metadata without proper path resolution or containment checks. Exploitation requires open registration and an image-type profile field on the signup form. Successful exploitation can lead to remote code execution by deleting critical files such as wp-config.php.

References

Community reviews

Loading reviews…