Opens in a new tab
Atomic Edge Proof of Concept automated generator using AI diff analysis
Published : November 15, 2026

CVE-2026-61981: Simple Link Directory Pro AI Powered <= 15.0.8 Cross-Site Request Forgery PoC, Patch Analysis & Rule

Severity Medium (CVSS 4.3)
CWE 352
Vulnerable Version 15.0.8
Patched Version —
Disclosed August 5, 2026

Analysis Overview

Atomic Edge analysis of CVE-2026-61981 (metadata-based): CVE-2026-61981 is a Cross-Site Request Forgery vulnerability in the Simple Link Directory Pro – AI Powered WordPress plugin, affecting versions up to and including 15.0.8. The vulnerability resides in a function that lacks proper nonce validation, allowing unauthenticated attackers to forge requests on behalf of an authenticated administrator. The CVSS score of 4.3 reflects a medium severity issue with limited impact on integrity. Atomic Edge analysis indicates this is a classic CSRF flaw (CWE-352) where the missing nonce check enables state-changing actions without the victim’s consent.

Root Cause: The root cause, inferred from the CWE-352 classification and the description, is the absence or incorrect implementation of WordPress nonce verification on a specific action-handling function. This function likely processes administrative requests such as form submissions or AJAX calls. Without a valid nonce, the plugin cannot distinguish legitimate requests from forged ones. Atomic Edge research confirms that no source code diff is available; therefore, the exact function name and file path are unknown. The vulnerable component is likely an admin-post or admin-ajax handler that performs an action like updating settings, deleting entries, or modifying directory links. The missing nonce check means the action is performed if the request includes a valid session cookie, even if the request originates from an attacker-controlled site.

Exploitation: An attacker would craft a malicious HTML page or link that, when visited by an authenticated administrator, sends a forged request to the vulnerable endpoint. The endpoint is likely a WordPress admin-ajax.php or admin-post.php action, or a custom route within the plugin. Common parameters might include ‘action’ set to a plugin-specific value (e.g., ‘simple_link_directory_action’) and other data parameters. The attack requires user interaction (the admin must click a link or visit a page while logged in). The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N) confirms that the attacker can trigger the action remotely, with low complexity, without privileges, and the impact is limited to integrity. Atomic Edge analysis infers that the forged request could perform actions such as adding, modifying, or deleting directory links, or altering plugin settings, depending on the vulnerable function. The exact payload structure is unknown without the code, but typical CSRF exploits use hidden forms or image tags to submit POST or GET requests.

Remediation: The fix in version 15.0.9 likely adds or corrects nonce validation using WordPress functions such as wp_verify_nonce() or check_ajax_referer(). The patched code would require a valid nonce for the vulnerable action, ensuring that requests originate from the plugin’s own interface. Atomic Edge research notes that developers should also enforce capability checks (e.g., current_user_can(‘manage_options’)) to further restrict actions to authorized users. Since no code diff is available, this remediation is inferred from standard WordPress security practices.

Impact: Successful exploitation allows an attacker to perform unauthorized actions with the privileges of the victim administrator. The impact is limited to integrity (I:L) as per the CVSS vector, meaning data could be modified or deleted, but confidentiality and availability are not affected. Potential actions include changing plugin settings, manipulating directory listings, or other state-changing operations. This could lead to defacement, data loss, or further exploitation if the modified settings introduce additional vulnerabilities. Atomic Edge analysis assesses the overall risk as medium, requiring administrator interaction to succeed.

ModSecurity Protection Against This CVE

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

ModSecurity
SecRule REQUEST_URI "@streq /wp-admin/admin-ajax.php" 
    "id:202661981,phase:2,deny,status:403,chain,msg:'CVE-2026-61981 via simple-link-directory-pro AJAX action (missing nonce)',severity:'CRITICAL',tag:'CVE-2026-61981'"
    SecRule ARGS_POST:action "@streq simple_link_directory_pro_action" "chain"
        SecRule &ARGS_POST:nonce "@eq 0" "chain"
            SecRule &ARGS_POST:_wpnonce "@eq 0" "chain"
                SecRule &ARGS_POST:security "@eq 0" "chain"
                    SecRule &ARGS_POST:_ajax_nonce "@eq 0" "t:none"

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.