CVE-2026-28134
8.5Crocoblock · JetEngine
A code injection vulnerability in the Crocoblock JetEngine WordPress plugin allows remote code inclusion by authenticated users.
Executive summary
A critical code injection vulnerability in Crocoblock JetEngine allows authenticated attackers to execute arbitrary code on the host server.
Vulnerability
This vulnerability involves improper control of code generation, specifically a code injection flaw that enables remote code inclusion. Per the CVSS vector, this requires an attacker to possess low-level privileges (authenticated) to trigger the exploit.
Business impact
The ability to perform remote code inclusion poses a severe threat to business operations, as it can lead to full server compromise, unauthorized access to sensitive database information, and the installation of persistent backdoors. With a CVSS score of 8.5, this vulnerability is classified as High severity and carries significant risk for organizations relying on the JetEngine plugin for dynamic content management.
Remediation
Immediate Action: Since no specific patch version is currently confirmed, administrators should immediately disable the JetEngine plugin until the vendor releases a security update that addresses the vulnerability.
Proactive Monitoring: Security teams should audit web server access logs for suspicious requests involving unexpected PHP execution or unauthorized file modifications within the WordPress plugin directory.
Compensating Controls: Implement a Web Application Firewall (WAF) with rules configured to detect and block common code injection patterns and malicious payloads targeting the WordPress environment.
Exploitation status
Public Exploit Available: Yes, a public proof-of-concept exists as documented in the GitHub repository maintained by RandomRobbieBF.
Analyst recommendation
Given the severity of this code injection flaw and the existence of a public proof-of-concept, organizations must treat this as a high-priority risk. Administrators should immediately restrict plugin access or deactivate the component until Crocoblock provides a verified security patch to remediate the vulnerability.
More Crocoblock CVEs
Sources
Originally found and disclosed by stealthcopter | Patchstack Bug Bounty Program, per the CVE Program record.