CVE-2025-69333
Missing Authorization in Crocoblock JetEngine Allows Unauthorized Access
Publication date: 2026-01-07
Last updated on: 2026-04-23
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| crocoblock | jetengine | From 3.0.0 (inc) to 3.8.1.1 (inc) |
| crocoblock | jetengine | 3.8.1.2 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-862 | The product does not perform an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-69333 is a broken access control vulnerability in the WordPress JetEngine plugin (up to version 3.8.1.1). It occurs due to missing authorization, authentication, or nonce token checks in certain functions, which allows users with Contributor or Developer privileges to perform actions that should be restricted to higher-privileged roles. [1]
How can this vulnerability impact me? :
This vulnerability could allow users with lower privileges (Contributor or Developer) to execute actions reserved for higher-privileged users, potentially leading to unauthorized changes or access within the WordPress site. However, the CVSS score of 4.3 indicates a low severity and low priority, and it is unlikely to be exploited with significant impact. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection involves identifying if your WordPress site is running JetEngine plugin version 3.8.1.1 or earlier. Since the vulnerability allows unprivileged users with Contributor or Developer roles to perform unauthorized actions, monitoring for unusual privilege escalations or unauthorized actions by these roles can help detect exploitation attempts. Specific commands are not provided, but checking the plugin version via WordPress admin or using WP-CLI commands like 'wp plugin list' to verify the JetEngine version is recommended. [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to update the JetEngine plugin to version 3.8.1.2 or later, where the vulnerability is fixed. Additionally, restricting user roles and permissions to prevent unprivileged users from performing higher-privileged actions can reduce risk. Using automated update tools or services like Patchstack's rapid vulnerability mitigation is also advised. [1]