Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-73993 – Unauthenticated PHP Object Injection – Roxnor FundEngine (wp-fundraising-donation)

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-73993 is an unauthenticated PHP Object Injection (deserialization of untrusted data) vulnerability affecting the Roxnor FundEngine WordPress plugin (package wp-fundraising-donation), used to build donation and crowdfunding pages. The flaw affects all versions up to and including 1.7.9 and carries a CVSS v3.1 score of 9.8 (Critical), as it can be triggered remotely over the network without authentication or user interaction.

Technical details

  • Root cause: the plugin deserializes untrusted, attacker-controlled input using PHP’s native unserialization functionality (CWE-502), rather than safe data formats.
  • Trigger conditions: an attacker submits crafted serialized data to a plugin endpoint/parameter that is passed into PHP’s deserialization routine; no login or interaction from a victim is required.
  • Attack vector: network-based (AV:N), low attack complexity, no privileges required, no user interaction required.
  • Impact: successful object injection can lead to secondary impacts such as arbitrary object instantiation and, depending on available "magic methods"/gadget chains in the WordPress/plugin environment, may result in remote code execution, data manipulation, or denial of service, consistent with the CVSS impact ratings of High confidentiality, integrity, and availability.

Affected software

  • Roxnor FundEngine – Donation and Crowdfunding Platform (WordPress plugin, package wp-fundraising-donation): versions up to and including 1.7.9
  • Fixed in version 1.8.0

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Update the FundEngine plugin (wp-fundraising-donation) to version 1.8.0 or later, where the deserialization issue is fixed.
  • If immediate patching is not possible:
    • Restrict or disable public access to the plugin’s donation/form submission endpoints until patched.
    • Deploy a web application firewall (WAF) rule to detect and block PHP serialized-object payloads in incoming requests to the plugin.
    • Monitor web server and application logs for anomalous POST requests containing serialized PHP object strings (e.g., beginning with O: or a:).
    • Take regular backups and review site integrity for signs of compromise if the plugin has been internet-exposed prior to patching.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw response body: /wp-content/plugins/wp-fundraising-donation/

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge