dbcve.org
Path TraversalWeakness · CWE-22

CVE-2024-12035

HIGH · 8.8 CVSS v3.1 Published 2025-03-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 CS Framework plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the cs_widget_file_delete() function in all versions up to, and including, 6.9. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php).

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 CS Framework WordPress plugin contains an arbitrary file deletion vulnerability in the cs_widget_file_delete() function due to insufficient path validation. Authenticated users with Subscriber-level access can manipulate file paths to delete arbitrary files on the server, potentially leading to remote code execution by deleting critical files like wp-config.php.

MitigationUpdate the plugin to a version beyond 6.9 if available, or implement strict path validation in cs_widget_file_delete() to prevent path traversal attacks and restrict deletions to allowed directories only.

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
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. Locate CS Framework plugin installation
    Check WordPress plugins directory (wp-content/plugins/) for the cs-framework folder, or view installed plugins in WordPress admin under Plugins > Installed Plugins
    Affected if CS Framework plugin is installed and active on the WordPress site
  2. Identify installed plugin version
    Read the main plugin file header (e.g., cs-framework.php) and look for the 'Version:' tag, or check the plugin row in WordPress admin plugins list
    Affected if Version is 6.9 or lower (the vulnerability exists in versions up to and including 6.9)
  3. Verify vulnerable function exists
    Search plugin source files for 'cs_widget_file_delete' function definition - typically in includes/cs-widget.php or similar include files within the cs-framework directory
    Affected if The cs_widget_file_delete() function is present in the codebase
  4. Check subscriber-level user access
    In WordPress admin, go to Users > All Users and review user roles. Alternatively, check if the site allows user registration with Subscriber role (Settings > General > Membership: anyone can register)
    Affected if Any user with Subscriber role exists, or open registration to Subscriber role is enabled, allowing authenticated access to the vulnerable function

If CS Framework plugin version 6.9 or lower is installed with the cs_widget_file_delete function exposed to Subscriber-level users, the site is vulnerable to arbitrary file deletion via path traversal.

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 the plugin to a version beyond 6.9 if available, or implement strict path validation in cs_widget_file_delete() to prevent path traversal attacks and restrict deletions to allowed directories only.

Recommended fix Moderate confidence

Version 7.0 or latest available release

  1. Check WordPress admin panel for CS Framework plugin updates
  2. Update CS Framework plugin to the latest available version (version 7.0 or higher if available)
  3. Verify the update was successful and the plugin is functioning correctly
  4. If automatic updates are enabled, ensure auto-update is configured for this plugin to receive future security patches
Caveat Minor - this appears to be a security patch release; always backup your site before updating

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
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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