dbcve.org
Tagdiv ComposerWordPress extension · Tagdiv

CVE-2024-5212

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_register_forum_user 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 contain a reflected Cross-Site Scripting vulnerability in the on_ajax_register_forum_user function. The envato_code[] parameter lacks proper input sanitization and output escaping, allowing unauthenticated attackers to inject arbitrary JavaScript via maliciously crafted URLs that execute when tricked users click the link.

MitigationUpdate tagDiv Composer to version 5.1 or later. Until patched, implement WAF rules to detect and block injection attempts in the envato_code[] parameter.

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. Verify tagDiv Composer is installed
    Check your WordPress installation's wp-content/plugins/ directory for a folder named 'tagdiv-composer' or access wp-admin > Plugins and look for 'tagDiv Composer' in the list of installed plugins.
    Affected if tagDiv Composer appears in your installed plugins list
  2. Check the installed version
    In WordPress admin, go to Plugins > Installed Plugins > tagDiv Composer and read the version number displayed. Alternatively, open wp-content/plugins/tagdiv-composer/readme.txt and check the version in the header section.
    Affected if The version is below 5.1 (versions 5.0 and lower are affected)
  3. Test for vulnerable AJAX endpoint exposure
    Send a request to your site's wp-admin/admin-ajax.php with parameters action=td_ajax_register_forum_user and envato_code[]=test. Use curl or a browser's developer tools to inspect the response.
    Affected if The page returns a response (rather than a 404 or '0' error) indicating the AJAX handler exists and processes the envato_code[] parameter
  4. Confirm XSS vulnerability exists in envato_code[] parameter
    Send a crafted request with a test XSS payload in the envato_code[] parameter (for example: envato_code[]=<script>alert(1)</script>) to wp-admin/admin-ajax.php?action=td_ajax_register_forum_user and examine whether the payload is reflected unescaped in the response HTML.
    Affected if The response reflects the raw payload without HTML encoding, confirming the XSS vulnerability is present

You are affected if tagDiv Composer is installed with a version below 5.1 and the vulnerable AJAX endpoint at admin-ajax.php responds to the td_ajax_register_forum_user action with unescaped envato_code[] parameter values.

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. Until patched, implement WAF rules to detect and block injection attempts in the envato_code[] parameter.

Recommended fix High confidence

Tagdiv Composer version 5.1

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Tagdiv Composer plugin in the list
  4. Check the current installed version (vulnerable if below 5.1)
  5. Click 'Update Now' to upgrade to version 5.1, or manually upload version 5.1 if automatic updates are not available
  6. After updating, verify the plugin shows version 5.1

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-5212 — 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-5212 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