CVE-2026-1947

The NEX-Forms – Ultimate Forms Plugin for WordPress plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 9.

Verified by Precogs Threat Research
Last Updated: Mar 16, 2026
Base Score
7.5HIGH

Executive Summary

CVE-2026-1947 is a high severity vulnerability affecting appsec. It is classified as CWE-639. Ensure your systems and dependencies are patched immediately to mitigate exposure risks.

Precogs AI Insight

"This exposure is a direct consequence of within The NEX-Forms –, allowing a lack of rigorous type checking mechanisms. This flaw provides a direct pathway for attackers to gain unauthorized read or write access, effectively hijacking underlying configurations. The Precogs AI's Code Property Graph analysis traces untrusted input to block malicious interactions before they reach production."

Exploit Probability (EPSS)
Low (0.0%)
Public POC
Undisclosed
Exploit Probability
Elevated (52%)
Public POC
Available
Affected Assets
appsecCWE-639

What is this vulnerability?

CVE-2026-1947 is categorized as a critical Application Verification Flaw flaw. Based on our vulnerability intelligence, this issue occurs when the application fails to securely handle untrusted data boundaries.

The NEX-Forms – Ultimate Forms Plugin for WordPress plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and inclu...

This architectural defect enables adversaries to bypass intended security controls, directly manipulating the application's execution state or data layer. Immediate strategic intervention is required.

Risk Assessment

MetricValue
CVSS Base Score7.5 (HIGH)
Vector StringCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
PublishedMarch 16, 2026
Last ModifiedMarch 16, 2026
Related CWEsCWE-639

Impact on Systems

Unauthorized Access: Flaws in application logic can permit unauthorized interaction with protected APIs.

Data Manipulation: Adversaries may alter critical application states, such as user roles or configurations.

Service Disruption: Improper error handling or unvalidated inputs can lead to resource exhaustion.

How to fix this issue?

Implement the following strategic mitigations immediately to eliminate the attack surface.

1. Defense in Depth Implement multi-layered validation (client-side, API gateway, and server-side).

2. Least Privilege Ensure backend service accounts operate with the absolute minimum rights required.

3. Security Regression Testing Integrate automated semantic security scanning into the deployment pipeline.

Vulnerability Signature

// Generic Application Security Flaw (Node.js)
app.post('/api/update-profile', (req, res) =\> \{
    // DANGEROUS: Mass Assignment / Object Injection
    // Attacker can pass \{ "isAdmin": true, "email": "..." \}
    User.update(\{ id: req.user.id \}, req.body);
    
    // SECURED: Explicitly select permitted fields
    const \{ email, displayName, bio \} = req.body;
    User.update(\{ id: req.user.id \}, \{ email, displayName, bio \});
\});

References and Sources

Vulnerability Code Signature

Attack Data Flow

StageDetail
SourceUntrusted User Input
VectorInput flows through the application logic without sanitization
SinkExecution or Rendering Sink
ImpactApplication compromise, Logic Bypass, Data Exfiltration

Vulnerable Code Pattern

# ❌ VULNERABLE: Unsanitized Input Flow
def process_request(request):
    user_input = request.GET.get('data')
    # Taint sink: processing untrusted data
    execute_logic(user_input)
    return {"status": "success"}

Secure Code Pattern

# ✅ SECURE: Input Validation & Sanitization
def process_request(request):
    user_input = request.GET.get('data')
    
    # Sanitized boundary check
    if not is_valid_format(user_input):
        raise ValueError("Invalid input format")
        
    sanitized_data = sanitize(user_input)
    execute_logic(sanitized_data)
    return {"status": "success"}

How Precogs Detects This

Precogs AI Analysis Engine maps untrusted input directly to execution sinks to catch complex application security vulnerabilities.\n

Related Vulnerabilitiesvia CWE-639

CVE-2026-339316.5 MEDIUM

IDOR in OpenEMR Patient Portal payment page before 8.0.0.3. Authenticated patients can access other patients' payment and billing data (PHI) by manipulating the 'recid' parameter.

CWE-639
CVE-2026-339344.3 MEDIUM

IDOR in OpenEMR Patient Portal 'show-signature.php' before 8.0.0.3. Authenticated patients can retrieve staff member signature images by supplying arbitrary user values in the POST body.

CWE-639
CVE-2026-340558.1 HIGH

IDOR in OpenEMR library/pnotes.inc.php before 8.0.0.3. Legacy patient notes functions fail to verify ownership, allows users to access and manipulate notes of unauthorized patients.

CWE-639
CVE-2026-334250 UNKNOWN

Discourse is an open-source discussion platform.

CWE-203CWE-639CWE-862
CVE-2026-330538.8 HIGH

Langflow is a tool for building and deploying AI-powered agents and workflows.

CWE-639
CVE-2026-321140 UNKNOWN

Discourse is an open-source discussion platform.

CWE-639

Is your system affected?

Precogs AI detects CVE-2026-1947 in compiled binaries, LLMs, and application layers — even without source code access.