dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-7094

CRITICAL · 9.8 CVSS v3.1 Published 2024-08-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The JS Help Desk – The Ultimate Help Desk & Support Plugin plugin for WordPress is vulnerable to PHP Code Injection leading to Remote Code Execution in all versions up to, and including, 2.8.6 via the 'storeTheme' function. This is due to a lack of sanitization on user-supplied values, which replace values in the style.php file, along with missing capability checks. This makes it possible for unauthenticated attackers to execute code on the server. This issue was partially patched in 2.8.6 when the code injection issue was resolved, and fully patched in 2.8.7 when the missing authorization and cross-site request forgery protection was added. CVE-2024-43274 is likely a duplicate of this issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The JS Help Desk WordPress plugin has an unauthenticated PHP code injection vulnerability in the storeTheme function. Attackers can inject arbitrary PHP code via user-supplied values that get written to style.php, enabling full remote code execution. Missing authorization checks and CSRF protection compound this issue.

MitigationUpdate to version 2.8.7 or later immediately - this is an unauthenticated RCE vulnerability with CVSS 9.8 critical severity.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm JS Help Desk plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins, or check the /wp-content/plugins/ directory for the 'js-help-desk' folder
    Affected if The plugin is present in the WordPress installation
  2. Identify installed plugin version
    In the Plugins list, find the JS Help Desk entry and read the version number displayed beneath the plugin name, or inspect the main plugin file (e.g., js-help-desk.php) for the 'Version' header comment
    Affected if The version number is 2.8.6 or lower (any version up to and including 2.8.6)
  3. Check if vulnerable storeTheme endpoint is accessible
    Probe the site's REST API or ajax endpoint for the storeTheme function. This typically involves a POST request to /wp-admin/admin-ajax.php with action=storeTheme or a direct API call to the endpoint handling theme style modifications
    Affected if The storeTheme function responds without authentication requirements, indicating the missing authorization check is present
  4. Inspect style.php for suspicious modifications
    Locate the style.php file within the plugin directory (typically in a themes or assets folder). Open the file and search for any base64_decode, eval, shell_exec, system, or other code execution patterns that were not part of the original plugin
    Affected if The style.php file contains unfamiliar PHP code, encoded strings, or code that resembles web shells or remote execution payloads

A user is affected if the JS Help Desk plugin version is 2.8.6 or lower and the storeTheme function is accessible without authentication, or if the style.php file shows signs of unauthorized PHP code injection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to version 2.8.7 or later immediately - this is an unauthenticated RCE vulnerability with CVSS 9.8 critical severity.

Recommended fix High confidence

2.8.7

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'JS Help Desk – The Ultimate Help Desk & Support Plugin' in the list
  4. Click 'Update now' if an update is available, or manually upload version 2.8.7 or later
  5. Verify the plugin updated successfully to version 2.8.7 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-7094 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-7094 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data