---
title: "CVE-2026-104995: WordPress BP Profile Search - Local File Inclusion"
description: "BP Profile Search plugin for WordPress <= 5.9 contains a local file inclusion vulnerability caused by improper validation of the 'ajax_template' value from the 'bps_directory' cookie during BuddyPress AJAX requests, letting unauthenticated attackers include arbitrary PHP files, exploit requires attacker control over HTTP_REFERER and cookie."
url: https://panop.io/threat-heartbeat/CVE-2026-104995/
---

# CVE-2026-104995 WordPress BP Profile Search - Local File Inclusion

BP Profile Search plugin for WordPress <= 5.9 contains a local file inclusion vulnerability caused by improper validation of the 'ajax\_template' value from the 'bps\_directory' cookie during BuddyPress AJAX requests, letting unauthenticated attackers include arbitrary PHP files, exploit requires attacker control over HTTP\_REFERER and cookie.

CVSS base score 8.1 /10

High

CISA KEV

Not listed

Public exploit

None known

Authentication

Not required

EPSS

0.85% chance of exploitation in 30 days

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-104995)

## Details

Type

Local File Inclusion

Impact

Remote Code Execution

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Published

14 October 2026

Updated

15 October 2026

Weakness

[CWE-98](https://cwe.mitre.org/data/definitions/98.html)

## Vendor fix

Update to the latest version of BP Profile Search plugin.

Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them.

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-104995](https://nvd.nist.gov/vuln/detail/CVE-2026-104995)
- [https://plugins.trac.wordpress.org/changeset/3737650](https://plugins.trac.wordpress.org/changeset/3737650)
- [https://www.wordfence.com/threat-intel/vulnerabilities/id/a35419ff-a342-4480-9288-e98dee5afabc?source=cve](https://www.wordfence.com/threat-intel/vulnerabilities/id/a35419ff-a342-4480-9288-e98dee5afabc?source=cve)
- [https://plugins.trac.wordpress.org/browser/bp-profile-search/tags/5.9/bps-directory.php#L186](https://plugins.trac.wordpress.org/browser/bp-profile-search/tags/5.9/bps-directory.php#L186)
- [https://plugins.trac.wordpress.org/browser/bp-profile-search/tags/5.9/bps-directory.php#L408](https://plugins.trac.wordpress.org/browser/bp-profile-search/tags/5.9/bps-directory.php#L408)
- [https://plugins.trac.wordpress.org/browser/bp-profile-search/tags/5.9/bps-search.php#L6](https://plugins.trac.wordpress.org/browser/bp-profile-search/tags/5.9/bps-search.php#L6)
- [https://plugins.trac.wordpress.org/browser/bp-profile-search/tags/6.0/bps-directory.php](https://plugins.trac.wordpress.org/browser/bp-profile-search/tags/6.0/bps-directory.php)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)