WordPress BuddyPress Xprofile Custom Field Types plugin <= 1.3.1 - PHP Object Injection vulnerability

published 2026-10-29 11d ago modified 2026-10-29 11d ago also EUVD-2026-112988

cvss: 8.8; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 39%
public exploits: 0; none known

Subscriber PHP Object Injection in BuddyPress Xprofile Custom Field Types <= 1.3.1 versions.

Is CVE-2026-116868 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: total
Assessed: 11d ago (2026-10-29)

Exploit prediction

0.45% chance of exploitation in the next 30 days, higher than 39% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.1	8.8	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

BuddyDev BuddyPress Xprofile Custom Field Types

Classification

Weakness

CWE-502 Deserialization of Untrusted Data

Technology feeds

WordPress rss critical rss

References

patchstack.com /database/wordpress/plugin/bp-xprofile-custom-field-types/vulnerability/wordpress-buddypress-xprofile-custom-f
vdb-entry

Sources

CVE List CVE-2026-116868
NVD CVE-2026-116868

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.