dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-68554

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 Keenarch keenarch allows Using Malicious Files.This issue affects Keenarch: 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

Unrestricted file upload vulnerability in the Keenarch WordPress theme allows attackers to upload malicious files (e.g., PHP shells, executables) without proper validation, potentially leading to remote code execution on the server.

MitigationUpgrade Keenarch theme to version 2.0.1 or later. Additionally, implement server-side file type validation, restrict upload directories to non-executable permissions, and disable script execution 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 Keenarch theme version
    Navigate to WordPress admin dashboard > Appearance > Themes, locate Keenarch theme, and note the version number displayed. Alternatively, check the style.css file in the theme directory (wp-content/themes/keenarch/style.css) for the 'Version' header.
    Affected if The installed version is older than 2.0.1 (version not yet patched)
  2. Verify file upload endpoint accessibility
    Check if the theme includes any upload functionality by searching for upload-related PHP files in the theme directory (wp-content/themes/keenarch/). Look for files containing 'upload', 'file', or 'ajax' in their names. Attempt to access these endpoints via browser or curl to confirm they are reachable.
    Affected if Upload endpoints are publicly accessible without authentication or with weak access controls
  3. Inspect upload storage location
    Examine the theme's upload handling code to determine where uploaded files are stored. Check if uploads are saved within the webroot (wp-content/uploads/ or similar) versus outside the web-accessible directory structure.
    Affected if Uploaded files are stored in web-accessible directories (within /wp-content/uploads/ or similar)
  4. Check script execution permissions on upload directory
    If uploads are stored in a web-accessible location, verify whether .htaccess rules or server configuration prevent execution of PHP or other script files in that directory. Check for 'Options -Indexes' and 'php_flag engine off' directives in the .htaccess file of the upload directory.
    Affected if Script execution is not disabled in the upload directory (PHP files can be executed)

A user is affected if the Keenarch theme version is below 2.0.1 AND the upload functionality is accessible AND uploads are stored in web-accessible directories without script execution restrictions.

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 Keenarch theme to version 2.0.1 or later. Additionally, implement server-side file type validation, restrict upload directories to non-executable permissions, and disable script execution in upload directories.

Recommended fix Moderate confidence

Keenarch version 2.0.1 or later

  1. 1. Backup your current WordPress installation and database before making any changes
  2. 2. Navigate to the WordPress admin dashboard > Appearance > Themes
  3. 3. Deactivate the current Keenarch theme
  4. 4. Delete the existing Keenarch theme
  5. 5. Install the updated Keenarch theme version 2.0.1 or later from a trusted source (official theme provider or WordPress repository)
  6. 6. Activate the new version 2.0.1 of Keenarch theme
  7. 7. Verify the theme is functioning correctly and test file upload functionality if applicable
  8. 8. Monitor for any unusual activity after the update
Caveat No specific breaking changes documented; ensure custom child theme modifications are compatible with version 2.0.1

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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