Unrestricted File UploadWeakness · CWE-434

CVE-2025-9112

HIGH · 8.8 CVSS v3.1 Published 2025-09-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/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
The Doccure theme for WordPress is vulnerable to arbitrary file uploads due to incorrect file type validation in the 'doccure_temp_file_uploader' function in all versions up to, and including, 1.5.0. This makes it possible for authenticated attackers, with subscriber-level and above permissions, to upload arbitrary files on the affected site's server which may make remote code execution possible.

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 Doccure WordPress theme has an arbitrary file upload vulnerability in the 'doccure_temp_file_uploader' function due to insufficient file type validation. Authenticated users with subscriber-level permissions can upload arbitrary files, potentially including executable PHP files leading to remote code execution.

MitigationUpdate to version 1.5.1 or later if available. Until patched, restrict or disable the file upload functionality and implement server-side restrictions on upload directories (e.g., disable script execution in upload folders).

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 Doccure theme installation
    Navigate to Appearance > Themes in WordPress admin dashboard and confirm if the Doccure theme is active. Note the theme version displayed.
    Affected if Doccure theme is active and version is below 1.5.1
  2. Locate the vulnerable function in codebase
    Access the theme files via FTP or file manager. Search for the function 'doccure_temp_file_uploader' in the theme directory, typically found in includes or functions folders.
    Affected if The function 'doccure_temp_file_uploader' exists in the theme files
  3. Check for unrestricted upload capability
    Review the function code to confirm it lacks proper file type validation. Look for missing checks on file extensions or MIME types before moving uploaded files.
    Affected if The function permits files without validating extension or content type
  4. Inspect upload directories for suspicious files
    Navigate to the wp-content/uploads directory (or custom upload path configured). Search for .php files or other executable extensions in date-based folders.
    Affected if Unexpected PHP files or executable scripts are present in upload folders
  5. Audit WordPress user roles
    Go to Users > All Users in WordPress admin. Check if any users have 'Subscriber' role or higher that could access the vulnerable upload function.
    Affected if Subscriber-level or higher user accounts exist and can access the upload functionality
  6. Review access logs for upload activity
    Examine server access logs (Apache/nginx) for POST requests to the file upload endpoint. Look for uploads of .php or other executable file types.
    Affected if Logs show POST requests uploading file types other than images or documents

A user is affected if the Doccure theme is installed with a version prior to 1.5.1 and the vulnerable upload function is present and accessible to low-privilege users.

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 to version 1.5.1 or later if available. Until patched, restrict or disable the file upload functionality and implement server-side restrictions on upload directories (e.g., disable script execution in upload folders).

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-9112 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-9112 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