dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2026-24960

CRITICAL · 9.9 CVSS v3.1 Published 2026-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 →
100/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
Unrestricted Upload of File with Dangerous Type vulnerability in zozothemes Charety charety allows Using Malicious Files.This issue affects Charety: from n/a through < 2.0.2.

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

Unrestricted file upload vulnerability in the zozothemes Charety WordPress theme allows unauthenticated attackers to upload malicious files by exploiting insufficient file type validation. The lack of proper input validation permits dangerous file types (e.g., PHP scripts) to be uploaded and potentially executed.

MitigationUpgrade to Charety version 2.0.2 or later which should contain the fix. If patching is not immediately possible, disable file upload functionality or add interim web server-level restrictions to block executable file types in upload directories.

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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. Identify if Charety theme is installed
    Locate the theme directory (typically in wp-content/themes/charety or similar path depending on the CMS platform) and check for theme.json, style.css, or theme metadata files containing the version number
    Affected if The Charety theme directory exists and contains theme files with version information
  2. Determine the installed theme version
    Read the theme version from theme.json, style.css header, or any version file within the Charety theme directory
    Affected if The version is earlier than 2.0.2 or the version cannot be determined (treat as vulnerable)
  3. Locate file upload functionality
    Search theme PHP files for file upload forms, handling code, or functions that process uploaded files (look for enctype='multipart/form-data', move_uploaded_file, or similar upload-related functions)
    Affected if The theme contains file upload handling code that accepts user-supplied files
  4. Verify file type validation exists
    Examine the upload handling code for proper validation - check for mime type checking, file extension allowlists, or content-type verification before processing uploads
    Affected if No file type validation is performed, or only client-side validation exists without server-side enforcement
  5. Check upload storage configuration
    Inspect the theme configuration and upload handling code to determine where uploaded files are stored - verify if uploads are placed outside the webroot or if script execution is disabled in the upload directory
    Affected if Uploaded files are stored within the web-accessible directory and script execution is not disabled (no .htaccess restrictions or equivalent)

If the Charety theme is installed and its file upload functionality lacks proper server-side file type validation and secure storage configuration, the environment is affected by this vulnerability.

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

Upgrade to Charety version 2.0.2 or later which should contain the fix. If patching is not immediately possible, disable file upload functionality or add interim web server-level restrictions to block executable file types in upload directories.

Recommended fix Moderate confidence

Charety theme version 2.0.2 or later

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Appearance > Themes
  3. 3. Locate the Charety theme by zozothemes
  4. 4. Update the theme to version 2.0.2 or later
  5. 5. Verify the update was successful and the site functions normally

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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