Vulnerability report

Exploited in the wild High confidence Not in CISA KEV

CVE-2026-3300

Everest Forms Pro <= 1.9.12 Unauthenticated Remote Code Execution

WPEverest / Everest Forms Pro · * to <= 1.9.12

Severity
CVSS 9.8 · Critical
Confidence
High
Exploit status
Exploited in the wild
EPSS
41.0%
First observed
Last observed

Decision summary

What security teams need to know first

Direct answers before the deeper technical record.

What it is

CVE-2026-3300 is an unauthenticated vulnerability affecting WPEverest Everest Forms Pro. The Everest Forms Pro plugin for WordPress is vulnerable to Remote Code Execution via PHP Code Injection in all versions up to,...

Is it exploited?

Yes. KEV Intelligence tracks this CVE as a known exploited vulnerability. Confidence is high.

Who is affected?

WPEverest / Everest Forms Pro * to <= 1.9.12.

What should we do?

Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.

Overview

Everest Forms Pro <= 1.9.12 Unauthenticated Remote Code Execution

The Everest Forms Pro plugin for WordPress is vulnerable to Remote Code Execution via PHP Code Injection in all versions up to, and including, 1.9.12. This is due to the Calculation Addon's process_filter() function concatenating user-submitted form field values into a PHP code string without proper escaping before passing it to eval().

The sanitize_text_field() function applied to input does not escape single quotes or other PHP code context characters. This makes it possible for unauthenticated attackers to inject and execute arbitrary PHP code on the server by submitting a crafted value in any string-type form field (text, email, URL, select, radio) when a form uses the "Complex Calculation" feature.

Vendor Product Affected Status
WPEverest Everest Forms Pro Through 1.9.12 Affected
Published
31 Mar 2026
Exploitation Reported
05 Jun 2026
Attack vector
Remote
Complexity
Low
Privileges
None
User interaction
None

Tags

wordpress php nuclei_scanner

CVE References

Exploitation evidence

Why KEV Intelligence marks this CVE as exploited

Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.

Exploited in the wild

TheHackerNews

Recorded 05 Jun 2026

Independent exploitation attestation added to the KEV Intelligence record.

Proof of concept available

GitHub

Recorded 05 Jun 2026

Public scanner or PoC coverage increases practical exploitability.

Known exploited vulnerability sources

Per-source evidence links for KEV attestations are available through the KEV Intelligence Pro API.

Learn about Pro API access
Source Added
TheHackerNews First 2026-06-05 09:20 UTC
BleepingComputer 2026-06-06 14:20 UTC

Detection

Operational artifacts and observed signals

Make the evidence actionable in scanner, SOC, and edge-control workflows.

Observed signals

Request targets
0
User-Agents
0

Raw values available in Pro and Enterprise.

Virtual patch status

No KEV Intelligence virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.

Learn about virtual patches →

Scanner Artifacts

Scanner and exploit-framework references linked to this CVE.

Risk and context

Severity, weaknesses, and research context

CVSS v3.1

9.8 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS

41.0%

Recent mention · BleepingComputer

Critical Everest Forms Pro flaw exploited to take over WordPress sites

Hackers are actively exploiting a critical vulnerability (CVE-2026-3300) in the Everest Forms Pro plugin, which lets them take complete control of a WordPress website. [...]

Read full advisory

All Mentions

Recent mention · BleepingComputer

Critical Everest Forms Pro flaw exploited to take over WordPress sites

BleepingComputer · 06 Jun 2026

Hackers are actively exploiting a critical vulnerability (CVE-2026-3300) in the Everest Forms Pro plugin, which lets them take complete control of a WordPress website. [...]

Recent mention · TheHackerNews

Hackers Exploit Critical Everest Forms Pro WordPress Plugin Flaw to Take Over Sites

TheHackerNews · 05 Jun 2026

Threat actors are actively exploiting a critical security flaw in Everest Forms Pro, a WordPress plugin with about 4,000 active installations, to execute arbitrary code, leading to a complete site compromise. The vulnerability in question is CVE-2026-3300 (CVSS score: 9.8), a remote code execution bug impacting all versions of the plugin up to, and including, 1.9.12. A patch for the flaw was

Potential Proof of Concepts

These PoCs are unverified and could contain malware. Use at your own risk.

Timeline

From disclosure to observed exploitation

  1. Public PoC available

    Public proof-of-concept code published

  2. Nuclei template available

    Scanner coverage available

  3. KEV confirmed by BleepingComputer

    Exploitation attested by an external source

  4. Added to KEV Intelligence KEV Feed

    High-confidence, third-party attested exploitation

  5. CVE published

    Vulnerability disclosed publicly

  6. CVE ID reserved

    Identifier reserved by the CNA

Pro API

Automate this intelligence

Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.

  • Evidence confidence and provenance
  • First-party sensor telemetry
  • PoC and scanner references
  • Affected versions and enrichment
  • Automation-ready JSON delivery

GET /api/v2/pro/kevs/CVE-2026-3300

Free JSON includes basic KEV fields
{
  "cve_id": "CVE-2026-3300",
  "confidence": "High",
  "cvss_score": 9.8,
  "cvss_estimated": false,
  "epss_score": 0.40992,
  "exploit_status": {
    "exploited_in_the_wild": true,
    "active_exploitation_observed": false
  },
  "sensor_telemetry": { "attempts": 0, "sensors": 0 }
}

Early warning alerts

Get alerts on high-impact exploitation

Receive curator-selected alerts when exploitation activity warrants attention. Each alert includes the evidence and context needed to decide what requires attention now.

Occasional high-impact alerts. Unsubscribe anytime. See our Privacy Policy.