Skip to content
Applications

CVE-2026-32470

9.8
Critical
EPSS 0.38%Aug 19, 2026

Unauthenticated PHP object injection in FundEngine enabling RCE and full server compromise.

common questions

Is CVE-2026-32470 being exploited?

Not confirmed. CVE-2026-32470 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.38% probability of exploitation in the next 30 days.

How severe is CVE-2026-32470?

CVE-2026-32470 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-32470?

Not known from our data. No patch reference has been recorded for CVE-2026-32470, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-32470 affect?

CVE-2026-32470 affects FundEngine <= 1.7.9 (PHP web application). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-32470?

Isolate hosts, block public access, deploy WAF, monitor logs, apply vendor patch when released.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
FundEngine <= 1.7.9 (PHP web application)
impact

Unauthenticated PHP object injection allowing remote code execution, arbitrary file read/write and full server takeover.

action required

Immediate action required

affected versions
Roxnor FundEngine
  • affected<= 1.7.9

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free