Security readout for executives and security teams
Plain-English summary
CVE-2026-3300 is a critical WordPress plugin issue in Everest Forms Pro through 1.9.12. If a site uses the Complex Calculation feature, an unauthenticated visitor could submit form data that causes PHP code to run on the server. This can lead to full site compromise. No source provided confirms active exploitation.
Executive priority
Treat as urgent for any internet-facing WordPress site using Everest Forms Pro with Complex Calculation. Prioritize inventory, feature exposure review, and vendor-confirmed updating because successful exploitation could allow complete website takeover.
Technical view
Everest Forms Pro’s Calculation Addon process_filter() reportedly builds a PHP code string from submitted form fields and passes it to eval(). sanitize_text_field() does not make values safe for PHP code context. The issue is CWE-94, network-accessible, unauthenticated, low complexity, with CVSS 3.1 score 9.8.
Likely exposure
Public WordPress sites running Everest Forms Pro up to and including 1.9.12 are potentially exposed when forms use Complex Calculation with string-type fields such as text, email, URL, select, or radio.
Exploitation context
The vulnerability is remotely reachable without authentication or user interaction according to the CVSS vector and description. The provided sources do not identify exploitation in the wild, and the CVE is not marked as CISA KEV in the source bundle.
Researcher notes
The source bundle gives strong vulnerability mechanics but limited remediation detail. The affected CPE data appears incomplete, while the title and description identify Everest Forms Pro through 1.9.12. Do not assume a fixed version without confirming the vendor changelog or advisory.
Mitigation direction
- Identify WordPress sites running Everest Forms Pro and record the installed version.
- Review whether any forms use the Complex Calculation feature.
- Check WPEverest/Everest Forms changelog and vendor guidance for a fixed version.
- Update Everest Forms Pro when a vendor-confirmed fix is available.
- Disable or remove affected Complex Calculation forms until remediation is confirmed.
- Restrict administrative access and monitor impacted sites for suspicious changes.
Validation and detection
- Confirm Everest Forms Pro version is not 1.9.12 or earlier, if vendor guidance confirms a fix.
- Inventory forms using Complex Calculation and string-type input fields.
- Review web server and WordPress logs for unusual form submissions.
- Check file integrity and recently modified PHP files on exposed sites.
- Verify vendor changelog entries before declaring remediation complete.
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-94: 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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-3300 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.
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.9Primary CVE scoreVulnerability 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
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/389c0b89-e408-4ad5-9723-a16b745771f0?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/everest-forms/tags/3.4.3/includes/class-evf-form-task.php#L584CVE reference
- https://everestforms.net/changelog/CVE reference
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.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.