dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-68549

CRITICAL · 9.9 CVSS v3.1 Published 2026-02-20
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 Wiguard wiguard allows Upload a Web Shell to a Web Server.This issue affects Wiguard: 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 · moderate confidence

The Wiguard WordPress theme by zozothemes contains an unrestricted file upload vulnerability (CWE-434) in versions prior to 2.0.1. This allows unauthenticated attackers to upload dangerous file types, specifically web shells, directly to the web server's webroot, enabling remote code execution.

MitigationUpgrade to Wiguard version 2.0.1 or later which contains the security patch. As an interim measure, disable the file upload functionality or deploy a WAF rule to block executable file uploads until the update can be applied.

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 Wiguard theme is installed
    Check your web application or CMS theme directory for the presence of the Wiguard theme from zozothemes. Common locations include /wp-content/themes/wiguard/ for WordPress or similar theme folders for other platforms.
    Affected if Wiguard theme folder exists in the web application theme directory
  2. Determine the installed Wiguard version
    Locate the theme's version file, style.css, or package.json within the Wiguard theme folder. Open the file and look for a Version: or similar version declaration.
    Affected if The version number found is lower than 2.0.1 (e.g., 2.0.0, 1.x.x, or older)
  3. Check for file upload functionality in the theme
    Search the theme files for file upload handlers, forms accepting file uploads, or upload endpoints. Look for PHP files containing move_uploaded_file, $_FILES, or similar upload-related functions.
    Affected if File upload code exists and accepts files without proper validation extensions
  4. Inspect upload directories for suspicious files
    Check common upload directories within the theme (e.g., /uploads/, /assets/, /media/) for unfamiliar PHP files, shell scripts, or files with unusual extensions like .php, .phtml, .exe, .sh.
    Affected if Unknown PHP files or web shell scripts are present in upload directories

The environment is affected if Wiguard theme is installed with a version lower than 2.0.1 and file upload functionality is accessible without proper validation.

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 Wiguard version 2.0.1 or later which contains the security patch. As an interim measure, disable the file upload functionality or deploy a WAF rule to block executable file uploads until the update can be applied.

Recommended fix Moderate confidence

Wiguard version 2.0.1

  1. 1. Backup your entire WordPress site (database and files) before making any changes
  2. 2. Download Wiguard theme version 2.0.1 from the official zozothemes source (zozothemes.com) or your purchase account
  3. 3. Navigate to Appearance > Themes in WordPress admin dashboard
  4. 4. Either update the existing Wiguard theme through WordPress if an update notification appears, or upload the new version as a new theme and activate it
  5. 5. Verify the theme is running version 2.0.1 by checking the theme version in Appearance > Themes
  6. 6. Test critical site functionality to ensure the update did not break existing features
  7. 7. Remove any unused or suspicious files from the uploads directory, particularly any .php files that were not intentionally uploaded

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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