Skip to main content
Mallory
CriticalPublic exploit

Unauthenticated PHP Code Injection RCE in Everest Forms Pro Complex Calculation

IdentifiersCVE-2026-3300CWE-94· Improper Control of Generation of…

CVE-2026-3300 is a critical remote code execution vulnerability in the Everest Forms Pro WordPress plugin affecting all versions up to and including 1.9.12. The flaw is in the Calculation Addon’s process_filter() function, within the Complex Calculation feature, where user-supplied form field values are concatenated into a dynamically constructed PHP code string and then executed via eval(). Although input is passed through sanitize_text_field(), that function does not escape single quotes or other characters significant in PHP code context. As a result, an unauthenticated attacker can submit crafted input in string-type form fields such as text, email, URL, select, or radio fields, break out of the intended string context, and inject arbitrary PHP code for execution on the server.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows unauthenticated remote attackers to execute arbitrary PHP code in the context of the web server/PHP process, resulting in full site compromise. Observed post-exploitation activity includes creation of rogue WordPress administrator accounts via wp_insert_user(), which can then be used to upload webshells, deploy backdoors, modify site content, manipulate local data, and potentially pivot further within the hosting environment.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by disabling or removing the Everest Forms Pro plugin, or at minimum disabling forms that use the Complex Calculation feature until the update can be applied. Monitor and block exploitation attempts against /wp-admin/admin-ajax.php, review logs for requests from reported malicious IPs, and inspect WordPress user accounts for unauthorized administrators such as the observed username “diksimarina.” Where available, enable protective WAF rules such as those referenced by Wordfence.

Remediation

Patch, then assume compromise.

Upgrade Everest Forms Pro to version 1.9.13 or later. This is the patched release identified in the provided content as fully mitigating the issue. In addition to patching, administrators should audit WordPress administrator accounts for unauthorized users, especially any recently created rogue accounts, and review application and web server logs for exploitation attempts and indicators of compromise.
PUBLIC EXPLOITS

Exploits

1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.

VALID 1 / 1 TOTALView more in app
CVE-2026-3300MaturityPoCVerified exploit

Repository is a small standalone Python exploit project for CVE-2026-3300 targeting WordPress Everest Forms Pro <= 1.9.12. Structure is minimal: one executable Python script (cve-2026-3300.py), a README with usage examples, requirements.txt listing requests, and targets.txt containing sample URLs. The script is the clear entry point and implements four main modes: scan, poc, exploit, and reverse. Core capability: the exploit crafts unauthenticated POST requests containing a malicious value in an Everest Forms field parameter to trigger PHP code injection in the vulnerable calculation functionality. The payload generator supports multiple PHP execution primitives (system, exec, passthru, shell_exec) and appends a PWNED marker to help confirm successful execution. The exploit posts either to /wp-admin/admin-ajax.php with action=everest_forms_process_submission or to the site root / as a fallback. Success is inferred from HTTP 200 responses containing PWNED or common command-output indicators such as uid=, root:, www-data, or command not found. Reconnaissance capability: scan() performs lightweight detection by requesting /wp-json/everest-forms/v1/forms and /wp-admin/admin-ajax.php, looking for strings like everest or evf in responses. This is not a pure detector-only repository; it contains active exploitation logic. Post-exploitation capability: reverse mode builds a bash reverse-shell command using the local host IP and a chosen listener port, starts a threaded TCP listener bound to 0.0.0.0, and then reuses the exploit path to execute the reverse-shell command on the target. Batch operation is supported through targets.txt and ThreadPoolExecutor-based concurrency. Overall, this is an operational standalone web exploit/command-execution tool rather than a framework module. It is not heavily weaponized, but it does provide practical exploitation features beyond a simple proof of concept, including target scanning, configurable payload functions, multithreaded batch exploitation, and a basic interactive reverse-shell workflow.

HORKimhabDisclosed Jun 5, 2026pythonwebnetwork
EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
WpeverestEverest Forms Proapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity21

Community discussion across Reddit, Mastodon, and other social sources.