BuddyPress Xprofile Custom Field Types · Security record
Is BuddyPress Xprofile Custom Field Types safe?
One known vulnerability affects the current version (1.3.2), and it has no fix yet.
Checked 5 days ago against the WPVulnerability database, for version 1.3.2.
How it’s looked after
- Last release
- Nov 5, 2026 (5 days ago)
- Releases in the last year
- 4
- Tested up to
- WordPress 6.9.11 (current: 7.1)
- Support resolved
- 1 of 2 threads in two months
- Active installs
- 3K+
2 known vulnerabilities
- 2 high
1 affects the current version. 1 has no fix yet.
Every known vulnerability in BuddyPress Xprofile Custom Field Types
Newest first, with any that affect the current version at the top.
Affects the current version · No fix yet · CVE-2026-116868 · Oct 29, 2026 · Wordfence
Fixed in 1.3.0 · CVE-2025-14997 · Jan 5, 2026 · Wordfence
Questions about BuddyPress Xprofile Custom Field Types’s security
Is BuddyPress Xprofile Custom Field Types safe to use?
Yes: 1 known vulnerability affects version 1.3.2, according to WPVulnerability’s database. Until a fixed version is out, weigh the risk, or switch to an alternative.
Does BuddyPress Xprofile Custom Field Types have known security vulnerabilities?
Yes: 1 known vulnerability affects version 1.3.2, according to WPVulnerability’s database.
Is BuddyPress Xprofile Custom Field Types still maintained?
Yes. Its last release was 5 days ago. Its authors resolved 1 of the 2 support threads opened in the last two months.
Is BuddyPress Xprofile Custom Field Types compatible with the latest WordPress?
BuddyPress Xprofile Custom Field Types’s readme says it’s tested up to WordPress 6.9.11, while the current version is 7.1. That doesn’t mean it breaks, but its author hasn’t confirmed it works with the latest releases.
Hear about the next one first
Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.
Start freeVulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.