dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-68553

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 Lendiz lendiz allows Upload a Web Shell to a Web Server.This issue affects Lendiz: from n/a through < 2.0.1.

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 Lendiz WordPress theme from zozothemes contains an unrestricted file upload vulnerability (CWE-434) that allows attackers to upload arbitrary file types including PHP web shells to the web server. This can lead to remote code execution and full server compromise.

MitigationUpgrade to Lendiz version 2.0.1 or later which should contain proper file type validation. If immediate patching is not possible, disable the theme or restrict upload functionality at the web server level.

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 Lendiz theme is installed
    Access WordPress admin dashboard and navigate to Appearance > Themes, or inspect the wp-content/themes directory for a folder named 'lendiz' or similar
    Affected if The Lendiz theme from zozothemes is present in the WordPress installation
  2. Check installed theme version
    Inspect the style.css file within the theme folder for a 'Version:' header, or view theme details in WordPress admin under Appearance > Themes
    Affected if Version is present but lower than 2.0.1, or no version is declared
  3. Verify upload functionality exists
    Look for theme options, settings pages, or any file upload forms within the Lendiz theme (typically in theme admin panels or frontend upload widgets)
    Affected if The theme includes any file upload functionality that accepts user-submitted files
  4. Confirm upload destination is accessible
    Test or inspect the theme's upload handler script to determine if files are saved to a publicly accessible web directory (usually wp-content/uploads/)
    Affected if Uploaded files are stored in web-accessible locations without validation

A user is affected if the Lendiz theme from zozothemes is installed with a version lower than 2.0.1 and contains accessible file upload functionality.

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

Upgrade to Lendiz version 2.0.1 or later which should contain proper file type validation. If immediate patching is not possible, disable the theme or restrict upload functionality at the web server level.

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-2025-68553 — 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-2025-68553 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