External risk intelligence

FundEngine Unauthenticated PHP Object Injection Vulnerability.

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-32470

The vulnerability affects a WordPress plugin, which is a type of web application component. WordPress plugins are commonly deployed as part of public-facing web applications, making this surface likely to be reachable from the internet in typical deployments.

Deserialization

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

An unauthenticated PHP Object Injection vulnerability has been identified in FundEngine. This issue could allow an attacker to remotely execute code or compromise systems without needing any prior authentication. The primary concern is to confirm if your organization uses this specific technology and assess any potential exposure.

  • Unauthenticated code execution risk.
  • Affects FundEngine technology.
  • Confirm relevance and exposure.

Attack Path

How an attacker could exploit the issue

An unauthenticated attacker can exploit this vulnerability by sending a specially crafted PHP object to a vulnerable web application. This injection allows the attacker to execute arbitrary code on the server, potentially leading to complete system compromise.

  • No authentication required.
  • Injecting malicious PHP objects.
  • Remote code execution.

Live Threat

Current exploitation, exposure, and threat context

Unauthenticated PHP Object Injection in FundEngine could allow an attacker to execute arbitrary code or impact service availability when processing specially crafted serialized data. This could lead to the compromise of the affected system.

  • System code and configuration.
  • Via unauthenticated network requests.
  • Allows arbitrary code execution.

Operational Fix

Recommended remediation, mitigation, and detection steps

This critical vulnerability in FundEngine affects unauthenticated PHP object injection and requires immediate attention from teams responsible for web application security and platform management. The first step is to identify all instances of FundEngine, determine their reachability and business criticality, and locate the accountable owner to plan a risk-based remediation strategy.

  • Application owners are responsible for this issue.
  • Verify FundEngine's presence and exposure.
  • Plan remediation based on identified risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is FundEngine?

FundEngine is a WordPress plugin designed to facilitate fundraising and donation management on websites. It acts as an extension for WordPress, adding specific functionality for handling financial contributions and donor data directly within the content management system.

What does PHP Object Injection mean for CVE-2026-32470?

This vulnerability, classified as CWE-502, occurs when an application improperly handles serialized data. By sending a malicious PHP object to the plugin, an attacker can manipulate how the application processes information, potentially forcing it to execute unauthorized code on the host server.

How is this vulnerability triggered?

An attacker triggers this bug by sending a specially crafted, serialized PHP object to the web application via a network request. It is important to note that the vulnerability is not triggered by standard site traffic or administrative actions; it requires the specific, malicious data payload designed to exploit the object injection flaw.

Do I need to worry about this if my site is internal?

While internal sites face lower risk, Halo Surface Signal notes that WordPress plugins are frequently used in public-facing applications, making this vulnerability often reachable from the internet. You should assess whether your instance of FundEngine is accessible to external network traffic or restricted to internal users.

How should I respond to this vulnerability?

Your first step is to audit your environment to locate all active installations of FundEngine. Once identified, evaluate the accessibility of those systems and coordinate with the accountable application owners to prioritize risk-based remediation and prevent unauthorized code execution.

References