CVE-2025-66079
WordPress vulnerability analysis and mitigation

Overview

CVE-2025-66079 is a Missing Authorization (Broken Access Control) vulnerability in the Jegstudio Gutenverse Form WordPress plugin that allows authenticated low-privileged users to perform higher-privileged actions. It affects all versions of the plugin through 2.2.0, with version 2.3.0 released as the patched fix. The vulnerability was reported by Denver Jackson on October 29, 2025, and published by Patchstack on November 28, 2025. It carries a CVSS v3.1 base score of 6.5 (Medium) (Patchstack).

Technical details

The vulnerability is classified as CWE-862 (Missing Authorization), meaning the plugin fails to properly verify whether a requesting user has the appropriate permissions before executing sensitive functions. Specifically, the plugin lacks proper authorization, authentication, or nonce token checks in one or more functions, enabling a Contributor- or Developer-level authenticated user to invoke actions that should be restricted to higher-privileged roles. The attack vector is network-based, requires low privileges, and has low attack complexity with no user interaction needed (Patchstack).

Impact

Successful exploitation allows an authenticated low-privileged user (Contributor or Developer role) to perform unauthorized actions within the WordPress site, resulting in a high integrity impact. There is no confidentiality or availability impact identified. In practice, this could allow attackers to manipulate form configurations, data, or other plugin-controlled content beyond their intended permission scope (Patchstack).

Exploitability

No public proof-of-concept exploit code or in-the-wild exploitation has been reported for this vulnerability. The EPSS score is approximately 0.028%, indicating a very low probability of exploitation in the near term. Patchstack classifies this as low priority with no impactful threat, though they note that vulnerabilities of this class are sometimes used in mass-exploit campaigns targeting WordPress sites at scale. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog (Patchstack).

Exploitation steps

  1. Reconnaissance: Identify WordPress sites running the Gutenverse Form plugin version 2.2.0 or earlier using tools like WPScan or by inspecting plugin metadata in publicly accessible readme files.
  2. Obtain low-privileged access: Register or obtain credentials for a Contributor or Developer account on the target WordPress site.
  3. Identify unprotected endpoints: Enumerate the plugin's registered REST API routes or admin-ajax actions that lack proper capability checks or nonce validation.
  4. Send unauthorized request: Craft and submit an HTTP request (e.g., POST to the vulnerable AJAX action or REST endpoint) that invokes a privileged function, bypassing the missing authorization check.
  5. Achieve unauthorized action: Successfully execute a higher-privileged operation such as modifying form settings, accessing form submission data, or altering plugin configuration beyond the attacker's intended role (Patchstack).

Indicators of compromise

  • Logs: WordPress access logs showing unexpected POST requests to wp-admin/admin-ajax.php or REST API endpoints associated with the gutenverse-form plugin from low-privileged user accounts.
  • Logs: WordPress audit logs (if enabled) recording privilege-escalating actions performed by Contributor or Developer role accounts related to Gutenverse Form plugin functions.
  • File System: Unexpected changes to Gutenverse Form plugin configuration files or form data stored in the WordPress database (wp_options or custom plugin tables).
  • Network: Repeated or automated requests to Gutenverse Form plugin endpoints from the same authenticated session, potentially indicating scripted exploitation attempts.

Mitigation and workarounds

The vendor has released version 2.3.0 of the Gutenverse Form plugin, which addresses this vulnerability. Site administrators should update the plugin to version 2.3.0 or later immediately via the WordPress plugin dashboard. If an immediate update is not possible, consider temporarily deactivating the plugin or restricting Contributor/Developer role registrations until the patch can be applied. Patchstack users can enable auto-update for vulnerable plugins as an additional safeguard (Patchstack).

Community reactions

Patchstack, which coordinated the disclosure, classifies this as a low-priority vulnerability with no impactful threat, noting it is unlikely to be exploited despite the class of vulnerability being used in mass-exploit campaigns. The vulnerability was covered in the Wordfence Intelligence Weekly WordPress Vulnerability Report for the week of November 24–30, 2025 (Wordfence). No significant broader media coverage or notable researcher commentary has been identified.

Additional resources


SourceThis report was generated using AI

Related WordPress vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-16145HIGH7.2
  • gdpr-compliant-recaptcha-for-all-forms
NoYesAug 15, 2026
CVE-2026-18387MEDIUM6.5
  • groundhogg
NoYesAug 15, 2026
CVE-2026-16586MEDIUM6.5
  • contest-gallery
NoYesAug 15, 2026
CVE-2026-17090MEDIUM6.4
  • beaver-builder-lite-version
NoYesAug 15, 2026
CVE-2026-16146MEDIUM4.9
  • gdpr-compliant-recaptcha-for-all-forms
NoYesAug 15, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management