dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-13645

CRITICAL · 9.8 CVSS v3.1 Published 2025-04-04
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 tagDiv Composer plugin for WordPress is vulnerable to PHP Object Instantiation in all versions up to, and including, 5.3 via module parameter. This makes it possible for unauthenticated attackers to Instantiate a PHP Object. No known POP chain is present in the vulnerable software, which means this vulnerability has no impact unless another plugin or theme containing a POP chain is installed on the site. If a POP chain is present via an additional plugin or theme installed on the target system, it may allow the attacker to perform actions like delete arbitrary files, retrieve sensitive data, or execute code depending on the POP chain present.

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 allows unauthenticated PHP Object Instantiation via the module parameter in all versions up to 5.3. Attackers can instantiate arbitrary PHP objects, but without an existing POP chain in the plugin itself, exploitation requires another vulnerable plugin/theme on the target system that provides the chain for file deletion, data exfiltration, or code execution.

MitigationUpdate tagDiv Composer to version 5.4 or later when available; alternatively, implement strict allowlist validation on the module parameter to prevent instantiation of untrusted classes.

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. Verify tagDiv Composer is installed
    Check the WordPress plugins directory or use WP CLI: wp plugin list --status=active --format=csv | grep composer
    Affected if The tagDiv Composer plugin appears in the list of active plugins
  2. Determine the installed version
    View the plugin header: wp plugin get td-composer --format=json or check wp-content/plugins/td-composer/readme.txt for the Version field
    Affected if The version number is 5.3 or lower (versions through 5.3 are vulnerable)
  3. Confirm the plugin is active and accessible
    The vulnerability is unauthenticated, meaning any frontend request can trigger the module parameter. Check that the plugin is actively loaded on the site.
    Affected if The plugin is active and responding to requests
  4. Audit for POP chain candidates
    Review all other installed plugins and themes for known deserialization vulnerabilities or POP chains (common candidates include plugins with unserialize() calls, certain form builders, and custom theme code using PHP magic methods)
    Affected if Other plugins or themes containing POP chains or unsafe unserialize() usage are present on the same WordPress installation

A user is affected if tagDiv Composer version 5.3 or lower is installed and active, and especially if other plugins/themes with POP chains exist that could be chained with the object instantiation.

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 tagDiv Composer to version 5.4 or later when available; alternatively, implement strict allowlist validation on the module parameter to prevent instantiation of untrusted classes.

Recommended fix Moderate confidence

tagDiv Composer version 5.4 or later

  1. 1. Check the current version of the tagDiv Composer plugin installed on your WordPress site
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Locate the tagDiv Composer plugin and note the current version number
  4. 4. Update the tagDiv Composer plugin to the latest available version (version 5.4 or higher)
  5. 5. After updating, verify the new version is installed correctly
  6. 6. Confirm the site functionality remains intact after the update
Caveat Minor or patch updates typically contain bug fixes and security patches with minimal risk of breaking changes

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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