CVE-2025-8420

Multiple Plugins by emarket-design <= Multiple Versions - Unauthenticated Limited Remote Code Execution

2025-08-05 13:47
mikemyers

Strategic Overview

Status
Patched in 6.0.3
Affected Version
<= 6.0.1
CVSS
8.1High
Weakness type
CWE-95 · Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection')
CVE
CVE-2025-8420
View all Customer Support Ticket System & Helpdesk vulnerabilities

At a glance

CVE-2025-8420 is a high-severity Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection') vulnerability in the Customer Support Ticket System & Helpdesk WordPress plugin, affecting versions <= 6.0.1. It carries a CVSS score of 8.1 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 6.0.3; sites on affected versions should update now. Disclosed August 2025, reported by mikemyers.

Vulnerability Overview

Multiple plugins for WordPress by emarket-design with the 'emd-form-builder-lite' package are vulnerable to Remote Code Execution in various versions via the emd_form_builder_lite_pagenum function. This is due to the plugin not properly validating user input before using it as a function name. This makes it possible for unauthenticated attackers to execute code on the server, however, parameters can not be passed to the functions called

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-95: Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection')

The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes code syntax before using the input in a dynamic evaluation call (e.g. eval).

Remediation

Update to version 6.0.3, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Customer Support Ticket System & Helpdesk 6.0.3 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Login Security

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C