dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2024-10436

HIGH · 8.8 CVSS v3.1 Published 2024-10-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 WPC Smart Messages for WooCommerce plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 4.2.1 via the get_condition_value function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.

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 WPC Smart Messages for WooCommerce WordPress plugin versions up to 4.2.1 contains a Local File Inclusion vulnerability in the get_condition_value function. Authenticated attackers with Subscriber-level access can exploit this to include arbitrary files on the server and execute embedded PHP code, potentially achieving remote code execution or accessing sensitive data.

MitigationUpgrade to version 4.2.2 or later which contains the patch. If immediate patching is not possible, disable the plugin until an update can be applied. The vulnerability requires authenticated access, so restricting user registration and reviewing subscriber-level accounts reduces exposure.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 WPC Smart Messages plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WPC Smart Messages for WooCommerce', or check the plugin files in wp-content/plugins/wpc-smart-messages/ for a main PHP file containing the version number
    Affected if The plugin is installed and active
  2. Identify the installed plugin version
    Open the main plugin PHP file (usually wpc-smart-messages.php) and locate the version defined in the plugin header comment, or check the version in the WordPress plugin admin UI
    Affected if Version is 4.2.1 or lower (any version up to and including 4.2.1)
  3. Check for subscriber-level user accounts
    In WordPress admin, go to Users > All Users and review the list for any accounts with the Subscriber role, or query the wp_users and wp_usermeta tables directly
    Affected if Any subscriber-level accounts exist in the system
  4. Verify the get_condition_value function is accessible
    Check if the plugin AJAX endpoint handling get_condition_value is accessible to authenticated users. Inspect the plugin source code for the function and verify the nonce/permission checks (or lack thereof) for the AJAX action
    Affected if The function is exposed without proper authorization checks or with subscriber-level access allowed

If the plugin is installed at version 4.2.1 or lower and subscriber-level users exist with access to the vulnerable function, the environment is affected by this CVE.

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

Upgrade to version 4.2.2 or later which contains the patch. If immediate patching is not possible, disable the plugin until an update can be applied. The vulnerability requires authenticated access, so restricting user registration and reviewing subscriber-level accounts reduces exposure.

Recommended fix Moderate confidence

4.2.2 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'WPC Smart Messages for WooCommerce' in the plugin list
  4. Click 'Update now' if an update is available, or manually download the latest version from wordpress.org
  5. If updating manually: deactivate the current version, delete it, then upload and install version 4.2.2 or higher
  6. Verify the update was successful by checking the plugin version

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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