CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →
← Back to Daily brief 2026-06-08
NOTABLECVE-2026-3300exploitedupdatedNATOB2vulnerability

CVE-2026-3300: unauthenticated code execution in Everest Forms Pro exploited since April to create rogue WordPress administrators, fixed in March

Attackers turned an Everest Forms Pro code-injection flaw, patched in March, into rogue admin accounts on WordPress sites

Analysis

CVE-2026-3300 (CVSS 9.8) is an unauthenticated remote code execution flaw in Everest Forms Pro, a commercial WordPress plugin with about 4,000 active installations, which Wordfence disclosed on 2026-03-30 after the vendor shipped the fix on 2026-03-18 (Wordfence, 2026-06-03). Attacker input reaches PHP evaluation through the plugin's calculation feature; the most common payload Wordfence sees closes a string literal and calls wp_insert_user() to create an administrator account (Wordfence, 2026-06-03). Attacks began on 2026-04-13 and peaked on 2026-05-16, when Wordfence blocked more than 17,900 attempts (Wordfence, 2026-06-03); The Hacker News and BleepingComputer reported the campaign in early June (The Hacker News, 2026-06-05) (BleepingComputer, 2026-06-06).

Cited evidence

attackers started actively targeting this vulnerability on April 13th, 2026, with mass exploitation occurring on May 16th, 2026

Wordfence 2026-06-03

Updates1

Correction

Wordfence published its exploitation report on 2026-06-03 and dates the peak to 2026-05-16, with more than 17,900 attempts blocked that day (Wordfence, 2026-06-03). The plugin has about 4,000 active installations, and no source names public-sector victims.

Sources3

Revision history

  1. Published 2026-06-08-1a0ce644
  2. Correction 2026-10-11T1307Z-audit

    Wordfence's report is dated 2026-06-03, not 2026-06-06; the mass-exploitation peak was on 2026-05-16, not sustained through June. The flaw sits in the complex-calculation feature of a plugin with about 4,000 installations; the public-sector exposure and SEO-spam injector claims had no source; and the summary, evidence and action carried workflow taglines and a broken fragment. The entry is rewritten from Wordfence with the campaign timeline, the rogue-administrator payload, exposure, detection and takeaway lines, verbatim evidence, a rating and an ATT&CK mapping.

    Changed: title headline summary sectors techniques affected_products cves sources evidence classification actions deep_dive deep_dive_category body event_date sourcing_note

PROVENANCE

AI-generated · no human review · this permalink is the shareable record for the finding · verify operationally critical claims against the linked primary source.