Everest Forms privilege escalation in plugin activation
Affects Everest Forms 3.6.4 and earlier on sites where non-admin roles are granted the everest_forms_create_forms capability, with a target plugin installed so it can be activated.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Summary
The Everest Forms WordPress plugin has a missing authorization check that lets a logged-in user with form-creation permission activate any installed but inactive plugin on the server over the network, which can lead to administrator-level privilege escalation. This applies only where an administrator has delegated that permission to a lower-privileged role.
Written by a model
Original description
The Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder with AI plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 3.6.4 This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with everest_forms_create_forms capabilities, to activate any already-installed inactive plugin on the server by supplying an arbitrary slug, triggering its activation hooks and escalating privileges up to administrator level. Exploitation requires that a site administrator has delegated the everest_forms_create_forms capability to a lower-privileged role via the plugin's Role & Permission feature, and that at least one inactive installed plugin whose main file follows the slug/slug.php naming convention exists on the server.
Who should check
WordPress sites running Everest Forms where non-admin roles hold the everest_forms_create_forms capability, such as sites using its Role & Permission settings
“The everest-forms/v1/plugin/activate and /plugin/upgrade REST routes”
What to do
Check whether your setup matches what the bug needs.
Non-admin roles are granted the everest_forms_create_forms (form-building) capability A target plugin is installed on the server so it can be activatedWorkaround: Until a fix is available, remove the everest_forms_create_forms capability from non-admin roles so that only trusted users can reach the affected route. The source gives no other vendor workaround.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-129220 (Everest Forms <= 3.6.4 - Authenticated (Custom+) Missing Authorization to Arbitrary Plugin Activation via 'moduleData' Parameter), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-129220 (entry last updated 2026-11-21):
Affected:
- wpeverest Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder with AI: through 3.6.4
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Non-admin roles are granted the everest_forms_create_forms (form-building) capability (source: https://github.com/themegrill/everest-forms/pull/1683)
- A target plugin is installed on the server so it can be activated (source: https://github.com/themegrill/everest-forms/pull/1683)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-129220 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129220 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/1b088ca1-d562-4543-9854-d0cf26c68c35?source=cve
- https://plugins.trac.wordpress.org/browser/everest-forms/tags/3.6.4/includes/RestApi/controllers/version1/class-evf-plugin-status.php#L297
- https://plugins.trac.wordpress.org/browser/everest-forms/tags/3.6.4/includes/RestApi/controllers/version1/class-evf-plugin-status.php#L462
- https://plugins.trac.wordpress.org/browser/everest-forms/tags/3.6.4/includes/RestApi/controllers/version1/class-evf-plugin-status.php#L147
- https://plugins.trac.wordpress.org/browser/everest-forms/tags/3.6.4/includes/RestApi/controllers/version1/class-evf-plugin-status.php#L223
- https://plugins.trac.wordpress.org/browser/everest-forms/tags/3.6.4/includes/RestApi/controllers/version1/class-evf-plugin-status.php#L262
- https://github.com/themegrill/everest-forms/pull/1683
- https://plugins.trac.wordpress.org/changeset/3811088/everest-forms/trunk/includes/RestApi/controllers/version1/class-evf-plugin-status.php
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-129220
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129220"}.Affected versions
- wpeverest Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder with AIthrough 3.6.4
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.8/10CVSS 8.8
- No patch5/5No patch listed yet
What would change the score
- Would score about 72 if added to CISA KEV
- Would score about 67 if CISA's SSVC rates exploitation active
- Would score about 29 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
Evidence 10
Questions about CVE-2026-129220
Is CVE-2026-129220 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
The REST route accepts a moduleData parameter and calls activate_plugin() on any installed plugin without an authorization check. Users who hold the form-building capability can use this to activate plugins they should not be able to activate, which is a privilege escalation.
Source: github.com
Which versions are affected by CVE-2026-129220?
Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder with AI: through 3.6.4.
Source: cve.now feed data
Am I affected, and how do I check?
Versions 3.6.4 and earlier of Everest Forms are in scope. The setup that matters is non-admin roles holding the everest_forms_create_forms capability, so check the installed version in the plugins list and check which roles hold that capability.
Source: github.com
How do I fix CVE-2026-129220?
The source names no fixed version or vendor patch, so no upgrade target is listed here. Check the vendor's advisory for an update before relying on any version.
Source: github.com
What if there's no patch?
Until a fix is available, remove the everest_forms_create_forms capability from non-admin roles so that only trusted users can reach the affected route. The source gives no other vendor workaround.
Source: github.com
Related
- CVE-2026-120513Everest Forms <= 3.6.2 - Unauthenticated Arbitrary File Deletion via 'everest_forms_{form_id}_old_{field_id}' Parameter
- CVE-2026-115483Everest Forms <= 3.6.3 - Unauthenticated Arbitrary File Read via 'Signature' Field Meta Key Branch of attach_entry_files
- CVE-2026-89101Everest Forms <= 3.6.2 - Insecure Direct Object Reference to Authenticated (Custom+) Arbitrary Entry/Form Disclosure and Deletion via MCP…
- CVE-2026-91152Everest Forms <= 3.6.2 - Reflected Cross-Site Scripting via 'evf_toast_type' Parameter
- CVE-2026-91153Everest Forms <= 3.6.2 - Unauthenticated Sensitive Information Exposure via Smart-Tag Injection in Smart-Tag Injection in Form Field Values ({post_meta key=...})
- CVE-2026-5096Everest Forms <= 3.4.4 - Unauthenticated Server-Side Request Forgery via Upload Field 'Previous Value'
No corrections so far. Something wrong on this page? Report an error.