Path TraversalWeakness · CWE-22

CVE-2024-13471

HIGH · 7.5 CVSS v3.1 Published 2025-03-05

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

84/100

Remediation priority · High

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

The DesignThemes Core Features plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the dt_process_imported_file function in all versions up to, and including, 4.7. This makes it possible for unauthenticated attackers to read arbitrary files on the underlying operating system.

Technical summary

dbcve analysis · high confidence

The DesignThemes Core Features WordPress plugin has a broken access control vulnerability in the dt_process_imported_file function. This function lacks a capability check, allowing any unauthenticated user to invoke it and read arbitrary files from the server's filesystem.

MitigationUpdate to version 4.8 or later which includes the missing capability check. If no update is available, disable the plugin or implement a temporary fix by adding a current_user_can() check to the dt_process_imported_file function.

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

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

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

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Verify DesignThemes Core Features plugin is installed

Check the WordPress plugins directory (wp-content/plugins/) for a folder containing 'designthemes' or check via WordPress admin Plugins page

Affected if The plugin appears in the installed plugins list
Determine the installed plugin version

Open the main plugin file (usually designthemes-core-features.php or similar) and locate the version header in the plugin comment block, or check the readme.txt file

Affected if The version is below 4.8 or the version cannot be determined (older or unmaintained installation)
Locate the vulnerable dt_process_imported_file function

Search the plugin files for the function name 'dt_process_imported_file' - typically found in import-export or core feature files

Affected if The function exists in the plugin codebase (indicating the vulnerable code is present)
Verify the function lacks capability checks

Examine the dt_process_imported_file function code to confirm there is no current_user_can() or similar permission check at the function entry point

Affected if The function has no capability check and is hooked to a publicly accessible action (like wp_ajax_nopriv or wp_ajax)

A user is affected if the DesignThemes Core Features plugin version is below 4.8 and the dt_process_imported_file function is present without capability verification.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Update to version 4.8 or later which includes the missing capability check. If no update is available, disable the plugin or implement a temporary fix by adding a current_user_can() check to the dt_process_imported_file function.

Recommended fix Moderate confidence

DesignThemes Core Features plugin version 4.8 or later (check WordPress plugin repository or ThemeForest for the latest fixed release)

Check the current version of the DesignThemes Core Features plugin installed on your WordPress site
Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
If the installed version is 4.7 or below, update the plugin to the latest available version that includes the security fix
After updating, verify the dt_process_imported_file function now includes proper capability checks
Consider reviewing file access permissions and monitoring for any suspicious access attempts

Caveat Review plugin settings after upgrade as default configurations may have changed

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

Have this fixed Scoped from the published advisory

Consultation2.0 h
Implementation2.0 h
Testing3.0 h
Review / QA2.0 h

9.0 hours of engineering $1,570

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-13471 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2024-13471?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsA vendor remedy is published

Severity 7.5 High

Exploit likelihood EPSS, next 30 days 0.5%

Remediation

A high-priority fix

Have this fixed 9 hrs · Moderate

Typical engagement from $1,570

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2024-13471 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References