dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-62047

CRITICAL · 9.9 CVSS v3.1 Published 2025-11-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 Case-Themes Case Addons case-addons.This issue affects Case Addons: from n/a through < 1.3.0.

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 Case-Themes Case Addons plugin allows attackers to upload files with dangerous types (e.g., PHP shells, executables) without proper validation, potentially leading to remote code execution on the affected WordPress site.

MitigationUpdate Case Addons to version 1.3.0 or later which contains the fix for proper file type validation; alternatively, implement server-side file type/mime type validation and restrict upload directories from executing uploaded files.

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. Check if Case Addons plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Case Addons' or 'Case-Themes Case Addons' in the installed plugins list
    Affected if Plugin is present and active in the WordPress installation
  2. Verify the installed version
    In WordPress admin > Plugins, click on the Case Addons plugin to view its version number, or check the plugin header in wp-content/plugins/case-addons/case-addons.php for the 'Version' comment
    Affected if Version is lower than 1.3.0 (e.g., 1.2.9, 1.2.8, etc.)
  3. Confirm file upload functionality is accessible
    Check if the plugin provides any frontend upload forms or admin upload features - look for upload endpoints in the plugin code (wp-content/plugins/case-addons/) or check if any Case Addons shortcodes or widgets related to uploads are in use
    Affected if Upload functionality is enabled and accessible to users or anonymous visitors
  4. Inspect upload directory accessibility
    Check the uploads directory (typically wp-content/uploads/) for any directories created by Case Addons, and verify if directory listing is enabled or if uploaded files can be accessed directly via web
    Affected if Uploaded files can be accessed directly via web URL (no access restrictions on the upload directory)

You are affected if the Case Addons plugin is installed with a version before 1.3.0 AND the file upload feature is enabled and accessible, allowing uploaded files to be served via web.

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

Update Case Addons to version 1.3.0 or later which contains the fix for proper file type validation; alternatively, implement server-side file type/mime type validation and restrict upload directories from executing uploaded files.

Recommended fix High confidence

1.3.0

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Navigate to the WordPress admin dashboard
  3. 3. Go to Plugins > Installed Plugins
  4. 4. Locate the Case Addons plugin
  5. 5. Check if the current version is below 1.3.0
  6. 6. If vulnerable, click 'Update Now' if an update is available, or download version 1.3.0 from a trusted source and upload it manually via Plugins > Add New > Upload Plugin
  7. 7. After updating, verify the new version number reflects 1.3.0 or higher
  8. 8. Test file upload functionality to ensure the plugin still works correctly

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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