dbcve.org
Wp Table ManagerWordPress extension · Joomunited

CVE-2024-13374

MEDIUM · 6.5 CVSS v3.1 Published 2025-02-12
Fix available
A fix is available. Upgrade to 4.1.4 or later.
See remediation →
71/100
Remediation priority · Elevated
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 WP Table Manager plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on thewptm_getFolders AJAX action in all versions up to, and including, 4.1.3. This makes it possible for authenticated attackers, with Subscriber-level access and above, to read arbitrary file names and directories.

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 WP Table Manager WordPress plugin lacks a capability check on the 'thewptm_getFolders' AJAX action, allowing any authenticated user with Subscriber-level permissions or higher to trigger this endpoint and read arbitrary file names and directories on the server via path traversal.

MitigationUpdate WP Table Manager to version 4.1.4 or later which includes the missing capability check. If immediate update is not possible, temporarily disable the plugin or add firewall rules to restrict the affected AJAX endpoint.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Wp Table ManagerWordPress extension
Affected:< 4.1.4

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
None
Availability
None

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

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 WP Table Manager plugin is installed
    Locate the plugin in the WordPress installation: check /wp-content/plugins/wp-table-manager/ directory, or query the WordPress database in wp_options for option_name = 'active_plugins', or use wp-cli: wp plugin list --name='wp-table-manager'
    Affected if The plugin directory or database entry exists and the plugin is active
  2. Determine installed plugin version
    Read the main plugin file header in /wp-content/plugins/wp-table-manager/wp-table-manager.php for the 'Version' field, or use wp-cli: wp plugin get wp-table-manager --field=version
    Affected if The version number is less than 4.1.4 (e.g., 4.1.3, 4.0.x, etc.)
  3. Verify AJAX endpoint is accessible
    Test if the thewptm_getFolders AJAX action responds. This can be done by sending a POST request to /wp-admin/admin-ajax.php with action=thewptm_getFolders. No nonce or capability check should be required for the vulnerability to exist. Check with: curl -k -X POST 'https://YOURSITE/wp-admin/admin-ajax.php' -d 'action=thewptm_getFolders'
    Affected if The endpoint returns a response without requiring authentication or elevated privileges (returns 200 OK rather than 403 or redirect to login)
  4. Check for existing users with Subscriber role or higher
    Query the WordPress users table (wp_users and wp_usermeta) for users with roles that include 'subscriber', 'contributor', 'author', 'editor', or 'administrator'. Use wp-cli: wp user list --role=subscriber --field=user_login --format=count
    Affected if At least one user account exists with Subscriber-level permissions or higher, making the vulnerability exploitable in practice

You are affected if WP Table Manager version is below 4.1.4 AND the plugin is active AND the AJAX endpoint responds without authorization AND at least one user with Subscriber role or higher exists on the 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.

dbcve · scoped
Upgrade available Upgrade to 4.1.4 or later
Fixed in 4.1.4
Interim mitigation

Update WP Table Manager to version 4.1.4 or later which includes the missing capability check. If immediate update is not possible, temporarily disable the plugin or add firewall rules to restrict the affected AJAX endpoint.

Recommended fix High confidence

WP Table Manager version 4.1.4

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate WP Table Manager in the plugin list
  4. 4. If the plugin shows an available update, click 'Update Now' to upgrade to version 4.1.4
  5. 5. Alternatively, navigate to Plugins > Add New > Upload Plugin to manually upload version 4.1.4 if automatic update is not available
  6. 6. Verify the installed version is 4.1.4 or higher after updating

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

Fix this in Wp Table Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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