dbcve.org
Tagdiv ComposerWordPress extension · Tagdiv

CVE-2024-3813

HIGH · 8.8 CVSS v3.1 Published 2024-06-15
Fix available
A fix is available. Upgrade to 4.9 or later.
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 tagDiv Composer plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 4.8 via the 'td_block_title' shortcode 'block_template_id' attribute. This makes it possible for authenticated attackers, with contributor-level and above permissions, 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 php file type 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 tagDiv Composer WordPress plugin is vulnerable to Local File Inclusion (LFI) in all versions up to 4.8. Authenticated attackers with contributor-level or higher permissions can exploit the 'td_block_title' shortcode's 'block_template_id' attribute to include and execute arbitrary files on the server, achieving PHP code execution.

MitigationUpdate tagDiv Composer to version 4.9 or later. Until patched, review and restrict user roles with contributor-level and above permissions, or temporarily disable the plugin if feasible.

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
Tagdiv ComposerWordPress extension
Affected:< 4.9

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. Verify tagDiv Composer plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'tagDiv Composer' or 'tagDiv Composer (formerly TagDiv Composer)' in the list. Note the installed version displayed.
    Affected if The plugin appears in the installed plugins list with a version below 4.9, or if the version column shows no version number or cannot be determined.
  2. Confirm the installed version number
    In the plugins list, locate the version number under the tagDiv Composer plugin name. Compare this against the affected range: versions less than 4.9 are vulnerable. If no version is shown, check the plugin's main PHP file header for the 'Version' field.
    Affected if The version number is less than 4.9 (for example: 4.8, 4.7, 4.6, 4.0, or any version starting with 4.x up to 4.8).
  3. Identify users with contributor-level or higher roles
    In WordPress admin, go to Users > All Users and review the Role column. Note any accounts assigned roles of Contributor, Author, Editor, or Administrator, as these roles can exploit the vulnerability.
    Affected if There is at least one user account with the Contributor, Author, Editor, or Administrator role active on the site.
  4. Verify the td_block_title shortcode is accessible
    Attempt to access a page or post editor, or view the site frontend. The vulnerability exists in the 'td_block_title' shortcode which is bundled with the plugin. If the plugin is active, this shortcode is available by default.
    Affected if The tagDiv Composer plugin is active and the td_block_title shortcode functions are loaded, regardless of whether the shortcode is actively used in content.

A user is affected if tagDiv Composer version is below 4.9 and there exists at least one user account with contributor-level or higher permissions on the 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.

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

Update tagDiv Composer to version 4.9 or later. Until patched, review and restrict user roles with contributor-level and above permissions, or temporarily disable the plugin if feasible.

Recommended fix High confidence

Tagdiv Composer version 4.9 or later

  1. Backup your WordPress site database and files
  2. Navigate to WordPress admin dashboard > Plugins
  3. Find Tagdiv Composer in the plugin list
  4. Click 'Update now' or manually update to version 4.9 or later
  5. Verify the installed version is 4.9 or higher after updating
  6. Test that the td_block_title shortcode functions correctly post-update

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

Fix this in Tagdiv Composer 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-3813 — 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-3813 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