☠️
EXFILTRATING
DATA...
01010111 10110010 00101001 11000110 01101100 10011011 00010001 11100101 01000010 10101111
[ <-- BACK_TO_SEARCH ]
Stellarwp logo [ WEBSITE ] [ VENDOR STATS ]
CVSS: 7.2 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H 🐛 CWE-266
👁️
Common Weakness Enumeration - Identifies the specific category of software weakness or flaw.

CVE-2025-54697

CVE-2025-54697 Privilege Escalation in Stellarwp
📅 PUBLISHED: 2025-08-14 11:15 UTC 🔄 UPDATED: 2026-08-12 14:52 UTC
[ PATCH UNDER REVIEW ↓ ] Remains UNDER REVIEW until an independent source confirms the fix
[ DEFENSE PATCH ↓ ]
💣 PoC: Public
👁️
Proof of Concept - Indicates if functional exploit code is publicly available, drastically increasing the risk of immediate attacks.
🎯 EPSS: 0.30%
👁️
0.30% probability
7.5× above the median CVE
Tier: ELEVATED
30-day exploitation window · FIRST.org · updated daily
🥷 MITRE: T1068
👁️
MITRE ATT&CK Tactic - Describes the strategy hackers use to execute this attack.
Country: Estonia License: Freemium
VULNERABLE: version not auto-detected — verify your deployed version locally
CVSS VECTOR BREAKDOWN 7.2
AV: N Attack Vector Network
AC: L Attack Complexity Low
PR: L Privileges Required Low
UI: N User Interaction None
S: U Scope Unchanged
C: H Confidentiality High
I: H Integrity High
A: H Availability High
7.2
THREAT LEVEL
■ tracking this CVE ✓ independent patch confirmation ⧗ same-origin mirror (GHSA) ⚠ active exploitation verification policy →

Executive Summary

CVE-2025-54697 is a critical privilege escalation vulnerability in the WordPress plugin Kadence WooCommerce Email Designer (kadence-woocommerce-email-designer), developed by StellarWP. The flaw stems from an incorrect privilege assignment (CWE-266) that allows authenticated attackers with low-level privileges (e.g., subscribers) to escalate their access to higher roles, potentially achieving administrative control over the WordPress site. The vulnerability affects all versions up to and including 1.5.16. With a CVSS score of 7.2, this issue poses a significant risk to e-commerce sites using WooCommerce, as it can lead to data breaches, site defacement, and further compromise of the underlying server.

⚡ AUTOMATE YOUR CVE INTELLIGENCE

This record — and 170,000+ others — are available via the ValtersIT API. One endpoint replaces five: NVD + GitHub CVE + CISA KEV + EPSS + Nuclei + Exploit-DB, unified.

›Patch confidence — UNVERIFIED to CONFIRMED, cross-referenced NVD + RHSA + Debian
›Exploit & PoC — poc_status, poc_url, has_exploit. Not in NVD.
›Shodan dorks — ready-made queries to find exposed vulnerable systems
›Detection rules — YARA · Wazuh · Elastic (all plans) · Sigma (Pro)
›pending_fields — know exactly which of 7 fields NVD hasn't processed yet
›Free backfill — data incomplete when you paid? Re-check within 30 days = 0 credits
PAYG €0.08/lookup Standard €19/mo (was €29) · 5k credits Pro €65/mo (was €99) · 20k credits FOUNDING PRICE · LOCKED FOR LIFE · ENDS 31 DEC 2026
[ FROM €19/MO ]
Free sandbox key available
No signup required

Supply Chain & Package Security

This vulnerability is specific to the WordPress plugin ecosystem. The plugin is distributed via the official WordPress Plugin Directory and third-party marketplaces. Users who installed the plugin from any source are affected. No official patch has been released by StellarWP, leaving all installations running version 1.5.16 or earlier at risk. Organizations should treat this as a supply chain risk and consider removing or disabling the plugin until a fix is available.

CVSS Breakdown & Threat Level

  • CVSS Score: 7.2 (High)
  • Attack Vector: Network (AV:N)
  • Attack Complexity: Low (AC:L)
  • Privileges Required: Low (PR:L) – attacker needs a valid user account (e.g., subscriber)
  • User Interaction: None (UI:N)
  • Scope: Unchanged (S:U)
  • Confidentiality Impact: High (C:H)
  • Integrity Impact: High (I:H)
  • Availability Impact: High (A:H)

Threat Level: High. The low attack complexity and low privileges required make this an attractive target for attackers. Successful exploitation can lead to full site compromise.

Deep Dive & Mechanics

The vulnerability resides in the plugin's role and capability checks when handling AJAX requests or admin actions. The plugin fails to properly validate user permissions before executing privileged operations, such as saving email templates or modifying plugin settings. Specifically, the wp_ajax_ hooks registered by the plugin do not enforce current_user_can() checks with appropriate capabilities (e.g., manage_options or edit_theme_options). Instead, they rely on weaker checks or none at all, allowing any authenticated user to invoke these functions.

An attacker with a subscriber account can craft a malicious AJAX request to the vulnerable endpoint, which then executes with the privileges of the WordPress installation, effectively escalating the attacker's role to administrator. The exact endpoint and parameters are not publicly documented, but the core issue is the missing or incorrect capability check.

Vulnerable vs. Patched Code

Since no official patch exists, the following is a hypothetical comparison based on the vulnerability type.

Vulnerable Code (version 1.5.16):

add_action('wp_ajax_kadence_woo_save_template', 'kadence_woo_save_template_callback');
function kadence_woo_save_template_callback() {
    // Missing capability check
    $template_data = $_POST['template'];
    // Process and save template...
    wp_send_json_success();
}

Patched Code (hypothetical fix):

add_action('wp_ajax_kadence_woo_save_template', 'kadence_woo_save_template_callback');
function kadence_woo_save_template_callback() {
    // Proper capability check
    if (!current_user_can('manage_options')) {
        wp_die('Unauthorized', 403);
    }
    $template_data = $_POST['template'];
    // Process and save template...
    wp_send_json_success();
}

The fix adds a current_user_can('manage_options') check, ensuring only administrators can execute the action.

Exploitation & Lab Setup

Red Team (Exploitation)

Prerequisites:

  • A WordPress site with Kadence WooCommerce Email Designer <= 1.5.16 installed and activated.
  • A valid user account with at least Subscriber role (e.g., username: attacker, password: attacker123).

Exploitation Steps:

  1. Obtain a nonce (if required): Some AJAX actions may require a nonce. Inspect the plugin's JavaScript to find the nonce value, often stored in a global variable or localize script.

  2. Craft the AJAX request: Use a tool like curl or a browser console to send a POST request to the WordPress admin-ajax.php endpoint.

    curl -X POST http://target-site/wp-admin/admin-ajax.php \
      -d "action=kadence_woo_save_template&template=malicious_content&_ajax_nonce=VALID_NONCE" \
      --cookie "wordpress_logged_in_attacker_session_cookie"
    
  3. Escalate privileges: If the vulnerable endpoint allows modifying user roles or creating admin accounts, the attacker can directly escalate. Otherwise, they may inject malicious PHP code into email templates that executes on admin page loads, leading to privilege escalation.

Note: No public exploit code is available, but the above methodology is standard for this class of vulnerability.

Blue Team (Detection & Defense)

Detection:

  • Monitor admin-ajax.php requests for unusual actions, especially from low-privilege users.
  • Look for rapid succession of AJAX calls from a single user to multiple endpoints.
  • Check for unexpected changes to user roles or new admin accounts.

Defense:

  • Immediately disable or remove the plugin until a patch is released.
  • Implement a Web Application Firewall (WAF) rule to block requests to admin-ajax.php with suspicious action parameters related to Kadence WooCommerce Email Designer.
  • Restrict user registration to trusted domains only.

Indicators of Compromise (IOCs)

  • File System: Presence of unexpected PHP files in wp-content/uploads/ or wp-content/plugins/kadence-woocommerce-email-designer/ with recent timestamps.
  • Database: New or modified user accounts with Administrator role, especially those with suspicious usernames.
  • Logs: Repeated admin-ajax.php requests from the same IP with parameters like action=kadence_woo_save_template.
  • Network: Outbound connections from the web server to unknown IPs (potential C2).

Detection Engineering

YARA Rule

rule CVE_2025_54697_Kadence_Woo_PrivEsc {
    meta:
        description = "Detects exploitation attempts for CVE-2025-54697 in Kadence WooCommerce Email Designer"
        author = "Valters IT"
        date = "2025-04-10"
        reference = "CVE-2025-54697"
    strings:
        $ajax_action = "kadence_woo_save_template" nocase
        $admin_ajax = "admin-ajax.php" nocase
        $post_data = "template=" nocase
    condition:
        all of them
}

Sigma Rule

title: CVE-2025-54697 Kadence WooCommerce Email Designer Privilege Escalation
id: 8a4b3c2d-1e5f-4a7b-9c8d-0e1f2a3b4c5d
status: experimental
description: Detects AJAX requests targeting the vulnerable Kadence WooCommerce Email Designer plugin
author: Valters IT
date: 2025/04/10
logsource:
    category: webserver
    product: apache
    service: access_combined
detection:
    selection:
        cs-method: 'POST'
        cs-uri-query|contains: 'admin-ajax.php'
        cs-uri-query|contains: 'action=kadence_woo_save_template'
    condition: selection
falsepositives:
    - Legitimate admin actions (rare)
level: high

Suricata Rule

alert http $HOME_NET any -> $EXTERNAL_NET any (msg:"CVE-2025-54697 Kadence WooCommerce Email Designer Privilege Escalation Attempt"; flow:to_server,established; content:"POST"; http_method; content:"admin-ajax.php"; http_uri; content:"action=kadence_woo_save_template"; http_client_body; classtype:attempted-admin; sid:1000001; rev:1;)

Remediation & Mitigation

Immediate Actions:

  1. Disable the plugin – Deactivate and delete the Kadence WooCommerce Email Designer plugin from all WordPress installations.
  2. Audit user accounts – Check for any unauthorized administrator accounts and remove them.
  3. Review logs – Examine web server and WordPress logs for signs of exploitation.

Long-term Fix:

  • Monitor the StellarWP website or WordPress Plugin Directory for an official patch. Apply it as soon as it becomes available.
  • If the plugin is critical, consider implementing a custom patch by adding capability checks to all AJAX handlers (as shown in the patched code example).

Workaround:

  • Use a security plugin (e.g., Wordfence) to block AJAX requests from low-privilege users to the vulnerable endpoints.

Valters IT

👁️ SHODAN DORKS (THREAT HUNTING)

What is this? Security researchers use these exact search queries on Shodan.io (a search engine for internet-connected devices) to find vulnerable systems globally. You can copy these dorks to see if your organization's IP space is exposed.

http.html:"wp-content/plugins/kadence-woocommerce-email-designer"
http.html:"kadence-woocommerce-email-designer"

💣 PoC CODE AVAILABLE

Exploit code for this CVE is tracked in our database. Access poc_code via API Pro.

[ API_PRO ] →
◈ SOURCE Analysis & enrichment: valtersit.com/cve/CVE-2025-54697/ · CVE data: NVD/MITRE (public domain) · © 2026 ValtersIT Hub
>_ SYSTEM_CORE: INTEL_ACTIVE
90% TEAM-CURATED // 10% AUTOMATED INGESTION.
ALL PATCH REFERENCES AND VERSION DATA SOURCED FROM NVD + OSV OFFICIAL REGISTRIES.