dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-49372

CRITICAL · 10.0 CVSS v3.1 Published 2025-11-06
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
Improper Control of Generation of Code ('Code Injection') vulnerability in VillaTheme HAPPY happy-helpdesk-support-ticket-system allows Remote Code Inclusion.This issue affects HAPPY: from n/a through <= 1.0.7.

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 · moderate confidence

A code injection vulnerability in the VillaTheme HAPPY helpdesk support ticket system plugin allows remote code inclusion due to improper control of code generation. This means an attacker can potentially include and execute malicious code from remote sources, leading to full system compromise of the WordPress installation.

MitigationDisable the plugin immediately if no patched version is available; otherwise, update to a fixed version. Implement strict input validation on all file inclusion functions to prevent arbitrary code execution.

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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. Verify HAPPY helpdesk plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for the 'happy-helpdesk' or 'happy' plugin folder, or query the WordPress database: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins';
    Affected if The plugin appears in the list of active or installed WordPress plugins.
  2. Identify installed plugin version
    Check the plugin main PHP file header for the 'Version' comment, or query the WordPress database: SELECT meta_value FROM wp_postmeta WHERE meta_key = '_plugin_version' AND post_id IN (SELECT ID FROM wp_posts WHERE post_type = 'plugin');
    Affected if The reported version is 1.0.7 or lower.
  3. Identify vulnerable file inclusion endpoints
    Review plugin PHP source code for dynamic include/require statements using $_GET, $_POST, or similar superglobals without proper sanitization. Look for patterns like: include($_GET['param']); or require($some_var);
    Affected if Dynamic file inclusion code exists that uses unsanitized user input.
  4. Check web server access logs for exploitation attempts
    Review Apache/nginx access logs for requests targeting the plugin with suspicious query parameters (e.g., ?action=include&file=, ?load=../). Search for: grep -E "(happy|helpdesk).*(file|include|require|load)" /var/log/apache2/access.log
    Affected if Requests with manipulated file inclusion parameters are found in logs.

You are affected if the HAPPY helpdesk plugin version is 1.0.7 or lower and the vulnerable file inclusion functionality is accessible/exposed on your WordPress site.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable the plugin immediately if no patched version is available; otherwise, update to a fixed version. Implement strict input validation on all file inclusion functions to prevent arbitrary code execution.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-49372 — 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-2025-49372 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