dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2026-40749

CRITICAL · 9.9 CVSS v3.1 Published 2026-06-17
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
Subscriber Arbitrary File Upload in Charity Zone <= 1.1.1 versions.

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 · moderate confidence

A critical arbitrary file upload vulnerability in Charity Zone plugin versions 1.1.1 and below allows authenticated subscribers to upload malicious files to the server, potentially achieving remote code execution.

MitigationUpdate Charity Zone plugin to version newer than 1.1.1 immediately; if no patched version exists, disable the plugin or restrict subscriber-level file upload capabilities until a fix is available.

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 Charity Zone installation
    Locate the Charity Zone plugin or theme files in the web root (commonly in wp-content/plugins/ or wp-content/themes/). Confirm the product exists on the system.
    Affected if Charity Zone plugin or theme is not found on the system
  2. Determine installed version
    Open the main plugin file or theme style.css header and locate the Version field. Compare this version number to 1.1.1 using standard version comparison (e.g., 1.1.1, 1.1.0, 1.0.9 are all <= 1.1.1).
    Affected if The installed version is 1.1.1 or lower
  3. Verify file upload functionality exists
    Locate the upload handler script or endpoint within the Charity Zone code (search for functions handling file uploads, move_uploaded_file, or wp_handle_upload). Confirm the upload mechanism is present.
    Affected if File upload functionality is present in the codebase
  4. Check Subscriber role upload access
    Examine the upload code for role-based access control. Determine if the Subscriber role (or equivalent low-privilege user) is permitted to access or trigger the upload function without elevated privileges.
    Affected if Subscriber-level users can access or trigger the file upload without administrator privileges

The environment is affected if Charity Zone version 1.1.1 or lower is installed AND the file upload feature is accessible to users with Subscriber-level privileges.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Charity Zone plugin to version newer than 1.1.1 immediately; if no patched version exists, disable the plugin or restrict subscriber-level file upload capabilities until a fix is available.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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