External risk intelligence

FundEngine Unauthenticated PHP Object Injection Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-73993

FundEngine is a WordPress plugin used for fundraising and donations. Such plugins are typically installed on public-facing web servers to process user interactions, contributions, and payment-related activities, making them commonly reachable from the internet in standard 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

This advisory concerns a critical unauthenticated PHP Object Injection vulnerability in the FundEngine plugin for WordPress. This type of vulnerability can allow an attacker to remotely execute code on a server without needing any credentials, potentially leading to a complete compromise of the affected system. The main concern is confirming if this plugin is in use and potentially exposed to the internet.

  • Attackers can inject malicious code remotely.
  • Critical vulnerability impacts public-facing websites.
  • Confirm relevance and exposure of the plugin.

Attack Path

How an attacker could exploit the issue

An unauthenticated attacker can exploit a PHP object injection vulnerability in FundEngine to execute arbitrary code. This occurs when the application processes serialized PHP data without proper validation, allowing an attacker to inject malicious objects. Successful exploitation could lead to a complete compromise of the affected system.

  • No authentication required for attack.
  • Triggered by processing untrusted serialized data.
  • Leads to arbitrary code execution.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could impact systems running the FundEngine plugin by allowing an unauthenticated attacker to inject PHP objects. When supported by the advisory, this could lead to the execution of arbitrary code or data manipulation on the affected server.

  • Plugin code and server-side operations.
  • Through crafted, unauthenticated requests.
  • Arbitrary code execution or data compromise.

Operational Fix

Recommended remediation, mitigation, and detection steps

This unauthenticated PHP object injection vulnerability in FundEngine affects publicly accessible WordPress sites, likely impacting application owners and web infrastructure teams. The first practical step is to confirm where FundEngine is deployed, assess its internet reachability and business criticality, identify the accountable owner, and then plan remediation based on risk.

  • Application owners should own the issue.
  • Verify external accessibility and business impact.
  • Plan remediation based on risk and vendor coordination.

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 the FundEngine plugin?

FundEngine is a WordPress plugin designed to facilitate fundraising and donation management. Because it processes financial contributions and user interactions directly on a website, it is often deployed on public-facing servers, which makes it a central component for managing donor data and campaign-related tasks.

How does this vulnerability work?

This issue is identified as CWE-502, or PHP Object Injection. It occurs because the plugin fails to properly validate serialized data before processing it. This technical oversight allows an unauthenticated user to supply specially crafted objects that the application then executes, potentially enabling remote code execution.

What actions trigger this vulnerability?

The vulnerability is triggered when the application processes untrusted serialized PHP data. Crucially, the attack does not require the user to have valid credentials or specific access permissions. It is a direct interaction with the plugin's data handling routines, meaning it is not limited by existing user roles.

Why is this plugin relevant for my environment?

According to the Halo Surface Signal, this plugin is likely to be reachable from the internet because it is typically installed on public-facing web servers to handle donor interactions. This network accessibility increases the risk profile for any system where the plugin is currently active.

How should I respond to this threat?

Start by identifying all instances where FundEngine is installed. Determine if these instances are accessible from the internet and evaluate their business criticality. Once mapped, coordinate with your infrastructure or application teams to prioritize remediation efforts based on the specific risk exposure of your assets.

References