Security readout for executives and security teams
Plain-English summary
FundEngine versions through 1.7.9 reportedly allow an unauthenticated attacker to submit unsafe serialized PHP data. Successful exploitation could compromise website data, integrity, and availability. The supplied evidence does not confirm exploitation in the wild or identify a verified patched version.
Executive priority
Treat as an urgent remediation item for internet-facing WordPress systems. Prioritize inventory, exposure reduction, and vendor-confirmed remediation because exploitation requires neither credentials nor user action and could affect the entire site.
Technical view
This is a network-accessible PHP object injection vulnerability classified as CWE-502. The CVSS 3.1 score is 9.8, with no authentication or user interaction required and high confidentiality, integrity, and availability impacts. Actual outcomes may depend on usable PHP object gadget chains in the WordPress environment.
Likely exposure
Internet-facing WordPress sites running the FundEngine plugin at version 1.7.9 or earlier are potentially exposed. The bundle's structured affected-version data is incomplete and internally inconsistent, so inventory verification is essential.
Exploitation context
No active exploitation is established by the supplied sources, and the CVE is not listed as KEV in the bundle. The low-complexity, unauthenticated network vector creates substantial risk, but available evidence does not describe observed attacks or confirmed exploit reliability.
Researcher notes
The title and description identify FundEngine through 1.7.9, but the structured affected entry says versions are unavailable and defaults to unaffected. No vulnerable endpoint, fixed version, patch details, exploit evidence, or prerequisites beyond the CVSS vector are supplied. Avoid asserting code execution without gadget-chain evidence.
Mitigation direction
- Identify all WordPress installations using FundEngine and record their installed versions.
- Check Roxnor and Patchstack guidance for a confirmed fixed release or official mitigation.
- Disable or remove affected plugin versions where operationally acceptable until remediation is confirmed.
- Restrict unnecessary public access and strengthen monitoring for suspicious requests and WordPress changes.
- Back up affected sites before remediation and protect backups from web-accessible modification.
Validation and detection
- Confirm FundEngine is absent or newer than the affected range on every WordPress instance.
- Verify the remediation version against current vendor or Patchstack guidance.
- Review web, application, and security logs for unusual unauthenticated requests to plugin functionality.
- Check WordPress files, administrators, scheduled tasks, and configuration for unauthorized changes.
- Perform defensive vulnerability scanning after remediation without using destructive tests.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-73993 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9PatchstackVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/wordpress/plugin/wp-fundraising-donation/vulnerability/wordpress-fundengine-plugin-1-7-9-php-object-injection-vulnerability-2?_s_id=cveCVE reference, Patchstack · vdb-entry
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.