Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRegister subscriber account on target site
-
DeliveryAuthenticate to WordPress
-
ExploitSend crafted request to unprotected FormGent endpoint
-
ExecutionBypass missing capability check
-
ImpactExfiltrate restricted form data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires a valid authenticated WordPress account at subscriber level or higher (PR:L) on a site running FormGent plugin version 1.12.2 or earlier; no user interaction and no special configuration are needed once such an account exists. The practical enabler is open user self-registration (a common WordPress setting), which lets an attacker obtain the required subscriber account at will; sites that disable registration or restrict account creation raise the bar significantly. The limiting factor is the plugin's niche deployment footprint and the requirement for at least subscriber authentication rather than fully unauthenticated access. |
| Impact | This is a moderate-priority authorization flaw whose real-world risk is meaningfully lower than its 7.1 CVSS score suggests. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N) shows a network-reachable, low-complexity issue requiring only low-privilege (subscriber-level) authentication and no user interaction, with high confidentiality impact and minor integrity impact - the score is driven almost entirely by C:H. No EPSS score, no CISA KEV listing, and no public proof-of-concept were provided, so there is no public exploit identified at time of analysis and no evidence of active exploitation. The single Patchstack reference confirms the vulnerability class (broken access control, CWE-862) but provides a sparse description that does not name the specific affected endpoint or the exact data exposed, so the C:H rating cannot be independently corroborated against a concrete data set. The main limiting factors are that any WordPress site allowing open user registration exposes subscriber accounts trivially, which raises reachability, but the affected product is a niche form-builder plugin with a small deployment footprint, which caps aggregate real-world exposure. Net: a real but not urgent issue - patch on a normal cadence rather than as an emergency. |
| Exploit ScenarioDerived | An attacker registers or obtains a low-privilege subscriber account on a WordPress site running FormGent <= 1.12.2, then sends a crafted authenticated request to a plugin function that lacks a proper capability check, retrieving form data or configuration the subscriber role should not be able to read. Because attack complexity is low and no user interaction is required, this can be scripted against any reachable site. No public proof-of-concept exploit was identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 30, 2026
Missing authorization checks in the FormGent WordPress plugin (versions through 1.12.2) allow an authenticated user holding only a subscriber-level account to reach form-management functionality and data normally reserved for higher-privileged roles, yielding high confidentiality impact and limited integrity impact. The flaw is network-reachable and needs no user interaction, but it does require a low-privileged account (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N, 7.1), so sites that permit open user self-registration are the most exposed while registration-restricted sites are considerably less at risk. No public exploit identified at time of analysis, and the vulnerability has not been confirmed as actively exploited (CISA KEV).
RemediationAI
No vendor-released patch was identified in the available data for CVE-2026-94499, so administrators should monitor the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/formgent/vulnerability/wordpress-formgent-plugin-1-12-2-broken-access-control-vulnerability?_s_id=cve) and update FormGent to the first published release documented as fixing this issue, or remove/deactivate the plugin if no fixed build appears. Until a fix is available, the highest-value compensating control is to close the account-creation path that makes the 7.1 score practical: disable 'Anyone can register' under WordPress Settings > General, review and delete existing subscriber accounts that are not strictly required, and block or rate-limit self-service registration endpoints, accepting the trade-off of losing self-service onboarding for legitimate users. Because the flaw requires only a subscriber session rather than any elevated role, restricting or removing the subscriber role from untrusted users materially raises the exploitation bar, and if the plugin's form-building and entry functionality is not business-critical, deactivating FormGent eliminates the exposed code paths entirely.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
FormGent is a WordPress form-builder plugin maintained by wpwax; the wildcard CPE cpe:2.3:a:wpwax:formgent:*:*:*:*:*:*:*:* identifies the affected product across tracked versions, with the advisory scoping the issue to release 1.12.2 and earlier. The root cause class is CWE-862 (Missing Authorization): the plugin's handler code for form-related operations - typically AJAX or REST entry points exposed to logged-in users - omits the current_user_can() capability check (or equivalent role gate) that should protect administrative or editor-level actions. Because the authorization check is absent rather than misconfigured, any account that can authenticate, including the lowest-privileged subscriber role, can reach the privileged code path and read data it should not be able to see, with a lesser ability to modify it. This is a broken function-level access control issue rather than an injection or cryptographic flaw, and exploitation depends solely on the attacker being able to obtain or hold a subscriber account on the target site.
Know when Formgent gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
Network-reachable plugin endpoint, low complexity, subscriber-level auth (PR:L), no interaction; CWE-862 disclosure gives C:H with minor I:L and no availability impact.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Subscriber Broken Access Control in FormGent <= 1.12.2 versions.
Executive ViewAI
The FormGent WordPress plugin (versions through 1.12.2) contains a missing authorization vulnerability that allows any authenticated subscriber-level user to access form-management data and functionality reserved for higher-privileged roles, resulting in high confidentiality impact. Sites with open user self-registration are most exposed, as attackers can easily create low-privileged accounts to exploit this flaw. Leadership should prioritize this because unauthorized disclosure of sensitive form submissions can harm customer trust and trigger regulatory compliance issues.
Disable open user registration; restrict subscriber accounts; deploy WAF/virtual patching to block unauthorized form-management access; deactivate the FormGent plugin if not business-critical. No vendor-released patch identified at time of analysis.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
EUVD-2026-89845
GHSA-gp7w-qv7j-pf87
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB