dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-6365

CRITICAL · 9.8 CVSS v3.1 Published 2024-07-09
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 Product Table by WBW plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 2.0.1 via the 'saveCustomTitle' function. This is due to missing authorization and lack of sanitization of appended data in the languages/customTitle.php file. This makes it possible for unauthenticated attackers to execute code on the server.

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 Product Table by WBW WordPress plugin is vulnerable to unauthenticated Remote Code Execution via the saveCustomTitle function in languages/customTitle.php. The vulnerability stems from missing authorization checks allowing any visitor to access the function and lack of input sanitization on user-supplied data, enabling attackers to inject and execute arbitrary code on the server.

MitigationUpdate the plugin to the latest version beyond 2.0.1 immediately. If no patched version is available, disable the plugin entirely and consider deploying a WAF rule to block requests to the vulnerable endpoint.

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 plugin installation
    Check if the Product Table by WBW plugin directory exists in your WordPress installation at wp-content/plugins/product-table-by-wbw/
    Affected if The plugin directory is present on the server
  2. Identify installed version
    Open the main plugin file (usually product-table-by-wbw.php) in the plugin directory and locate the 'Version' header in the plugin comment block, or check a version file if one exists
    Affected if The installed version is 2.0.1 or lower, or if the version cannot be determined but the plugin is present
  3. Verify vulnerable file exists
    Check if the file languages/customTitle.php exists within the plugin directory
    Affected if The file languages/customTitle.php exists in the plugin folder
  4. Check function accessibility
    Review the languages/customTitle.php file to confirm the saveCustomTitle function lacks authorization checks (look for missing current_user_can or similar capability checks before executing)
    Affected if The saveCustomTitle function can be accessed without authentication (no capability checks found)
  5. Test endpoint exposure
    If logs are available, review access logs for requests to languages/customTitle.php or its saveCustomTitle action endpoint
    Affected if Requests to the vulnerable endpoint are visible in web server logs from unauthenticated sources

Your environment is affected if the Product Table by WBW plugin version is 2.0.1 or lower, or if the languages/customTitle.php file exists and lacks authorization checks on the saveCustomTitle function.

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 the plugin to the latest version beyond 2.0.1 immediately. If no patched version is available, disable the plugin entirely and consider deploying a WAF rule to block requests to the vulnerable endpoint.

Recommended fix Moderate confidence

2.0.2 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Product Table by WBW' plugin
  4. Check if current version is below 2.0.2
  5. If vulnerable, click 'Update Now' to install the latest version
  6. Verify the update completed successfully

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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