dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-30996

CRITICAL · 9.9 CVSS v3.1 Published 2026-01-06
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 Themify Themify Sidepane WordPress Theme, Themify Themify Newsy, Themify Themify Folo, Themify Themify Edmin, Themify Bloggie, Themify Photobox, Themify Wigi, Themify Rezo, Themify Slide allows Upload a Web Shell to a Web Server.This issue affects Themify Sidepane WordPress Theme: from n/a through 1.9.8; Themify Newsy: from n/a through 1.9.9; Themify Folo: from n/a through 1.9.6; Themify Edmin: from n/a through 2.0.0; Bloggie: from n/a through 2.0.8; Photobox: from n/a through 2.0.1; Wigi: from n/a through 2.0.1; Rezo: from n/a through 1.9.7; Slide: from n/a through 1.7.5.

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 multiple Themify WordPress themes allows attackers to bypass file type restrictions and upload malicious PHP scripts (web shells) to the server, potentially achieving remote code execution and full system compromise.

MitigationUpdate all affected Themify themes to their latest patched versions immediately. If updates are unavailable, disable file upload functionality, implement strict file type validation server-side, and audit the server for existing web shells.

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 installed Themify themes
    In WordPress admin dashboard, go to Appearance > Themes to list all installed Themify themes. Alternatively, check /wp-content/themes/ directory via FTP or file manager for themes with 'themify' in the folder name.
    Affected if Any Themify theme is installed and active on the WordPress site
  2. Check Themify theme version
    In WordPress admin, go to Appearance > Themes and click on each Themify theme to view its details. Note the version number displayed, or inspect the style.css file in the theme folder for the 'Version:' header.
    Affected if The installed version falls within any known affected version range for this CVE
  3. Verify file upload functionality exposure
    Check if any Themify builder or theme feature that allows file uploads is accessible. Look for upload forms, builder settings, or file manager modules in the Themify theme/builder. Test by attempting to upload a non-image file through any Themify upload interface.
    Affected if File upload functionality is enabled and accessible to unauthenticated or low-privilege users
  4. Inspect uploaded files directory
    Check /wp-content/uploads/ folder (and any Themify-specific upload directories) for unexpected .php files, .phtml files, or scripts with suspicious names. Use file manager or FTP to list all files with these extensions.
    Affected if Any PHP files exist in upload directories that were not explicitly uploaded by administrators through the media library
  5. Review server for web shell indicators
    Search for recently created .php files across the web root, especially in /wp-content/, /wp-content/uploads/, and /wp-content/themes/. Look for files with random alphanumeric names, encoded content, or base64 strings indicating web shells.
    Affected if Suspicious PHP files or web shells are found on the server

A user is affected if they have any Themify theme installed with a version vulnerable to unrestricted file upload, and that upload functionality is exposed or any suspicious PHP files exist in upload directories.

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 all affected Themify themes to their latest patched versions immediately. If updates are unavailable, disable file upload functionality, implement strict file type validation server-side, and audit the server for existing web shells.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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