CVE-2025-58963
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 · uneditedUnrestricted Upload of File with Dangerous Type vulnerability in 7oroof Medcity medcity allows Upload a Web Shell to a Web Server.This issue affects Medcity: from n/a through < 1.1.9.
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 confidenceThe Medcity theme contains an unrestricted file upload vulnerability that allows attackers to upload malicious files (web shells) directly to the web server. This vulnerability has a CVSS 10 rating due to the potential for complete system compromise through remote code execution once the web shell is uploaded and accessed.
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
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Medcity theme is installedLocate the Medcity theme directory in the web application (typically in wp-content/themes/medcity or similar path) and confirm its presence on the server file system.Affected if The Medcity theme directory exists in the themes folder.
-
Determine the installed Medcity theme versionOpen the theme style.css file or theme.json file within the Medcity theme directory and read the Version: header value.Affected if The version is lower than 1.1.9 (e.g., 1.1.8, 1.1.0, or any version prior to the fix).
-
Locate file upload functionalitySearch the theme files (PHP templates, functions.php, or any upload-handling scripts) for file upload forms or $_FILES handling code.Affected if File upload handling code exists within the theme and accepts user-submitted files.
-
Verify file type validation is presentExamine the upload handling code to see if server-side validation checks the file extension or MIME type before saving the file.Affected if No server-side file type validation is performed, or validation can be bypassed, allowing script files (PHP, JSP, etc.) to be uploaded.
-
Check upload directory web accessibilityIdentify where uploaded files are stored and determine if that directory is accessible via the web server (within the web root).Affected if Uploaded files are stored in a web-accessible directory and script execution is not disabled in that location.
A user is affected if the Medcity theme is installed with a version lower than 1.1.9 and contains file upload functionality that lacks proper server-side validation or stores files in a web-accessible location.
Generated from the published advisory. Verify against your own configuration.
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 dataRestrict file uploads to safe file types (images, documents) with server-side validation, store uploads outside the web root, disable script execution in upload directories, and upgrade to version 1.1.9 or later.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58963 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-58963 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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