dbcve.org
Tagdiv ComposerWordPress extension · Tagdiv

CVE-2024-3886

MEDIUM · 6.1 CVSS v3.1 Published 2024-08-31
Fix available
A fix is available. Upgrade to 5.1 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Reflected Cross-Site Scripting via the ‘envato_code[]’ parameter in all versions up to, and including, 5.0 due to insufficient input sanitization and output escaping within the on_ajax_check_envato_code function. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.

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 (versions up to 5.0) contains a reflected XSS vulnerability in the on_ajax_check_envato_code function. The 'envato_code[]' parameter lacks proper input sanitization and output escaping, allowing unauthenticated attackers to inject arbitrary JavaScript via malicious URLs that execute when users click crafted links.

MitigationUpdate tagDiv Composer to version 5.1 or later, which implements proper input sanitization and output escaping for the envato_code[] parameter. Until then, warn users not to click untrusted links pointing to affected endpoints.

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:< 5.1

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 tagDiv Composer is installed
    Locate the tagDiv Composer plugin in your WordPress installation, typically under wp-content/plugins/td-composer/ or similar directory named after the plugin.
    Affected if The plugin directory exists on the server.
  2. Identify the installed version
    Open the plugin's main file (usually td-composer.php or composer.php) or the readme.txt file and locate the version declaration. Compare the version number to 5.1.
    Affected if The installed version is lower than 5.1 (for example: 5.0, 4.x, etc.).
  3. Verify the vulnerable AJAX endpoint is accessible
    Test access to wp-admin/admin-ajax.php with a request parameter including 'action=td_ajax_check_envato_code' and the 'envato_code[]' parameter. This endpoint handles the on_ajax_check_envato_code function.
    Affected if The AJAX endpoint responds and accepts the envato_code[] parameter without sanitization.
  4. Check if output escaping is missing
    Inspect the source code of the on_ajax_check_envato_code function in the plugin files. Look for the envato_code[] parameter handling and verify whether htmlspecialchars or equivalent escaping functions are used before outputting this parameter.
    Affected if The code does not use proper output escaping (such as htmlspecialchars, esc_attr, or esc_html) on the envato_code[] parameter before reflecting it in the response.

You are affected if tagDiv Composer is installed with a version lower than 5.1 and the envato_code[] parameter in the on_ajax_check_envato_code function lacks input sanitization and output escaping.

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 5.1 or later
Fixed in 5.1
Interim mitigation

Update tagDiv Composer to version 5.1 or later, which implements proper input sanitization and output escaping for the envato_code[] parameter. Until then, warn users not to click untrusted links pointing to affected endpoints.

Recommended fix High confidence

Tagdiv Composer version 5.1

  1. 1. Back up your WordPress site and database before making any changes
  2. 2. Navigate to the WordPress admin dashboard
  3. 3. Go to Plugins > Installed Plugins
  4. 4. Find the Tagdiv Composer plugin
  5. 5. If an update is available, click 'Update Now' to update to version 5.1
  6. 6. Alternatively, download version 5.1 from a trusted source and upload it via Plugins > Add New > Upload Plugin
  7. 7. After updating, verify the plugin version shows 5.1 or higher
  8. 8. Test that the envato_code functionality still works correctly

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

Fix this in Tagdiv Composer Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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