dbcve.org
UcmsApplication · Ucms Project

CVE-2023-1303

CRITICAL · 9.8 CVSS v3.1 Published 2023-03-09
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 No privileges 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
A vulnerability was found in UCMS 1.6 and classified as critical. This issue affects some unknown processing of the file sadmin/fileedit.php of the component System File Management Module. The manipulation of the argument file leads to unrestricted upload. The attack may be initiated remotely. The associated identifier of this vulnerability is VDB-222683.

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 UCMS 1.6's System File Management Module (sadmin/fileedit.php). Remote attackers can manipulate the 'file' argument to upload arbitrary files, potentially achieving remote code execution.

MitigationRestrict access to the sadmin directory and disable the fileedit functionality until a patch is available. Implement proper file type validation, size limits, and store uploads outside webroot.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
UcmsApplication
Affected:= 1.6

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Confirm UCMS installation and version
    Look for UCMS by checking the application for a version identifier. Common locations include: a /about or /admin/info page, a version.php file, a CHANGELOG or README file, or meta tags in the HTML source of the homepage.
    Affected if The installed version is exactly 1.6 (Ucms Project Ucms)
  2. Locate the sadmin directory
    Check if the 'sadmin' directory exists within the webroot of the UCMS installation. This is typically found at /sadmin/ relative to the main UCMS path.
    Affected if The sadmin directory exists and is publicly accessible via HTTP/HTTPS
  3. Verify fileedit.php exists
    Check for the presence of the fileedit.php file within the sadmin directory. Attempt to access sadmin/fileedit.php directly via a web request to confirm it is served.
    Affected if sadmin/fileedit.php exists and responds to requests
  4. Confirm file upload parameter is accepted
    Send a test request to sadmin/fileedit.php with a manipulated 'file' parameter. Observe whether the application accepts and processes the parameter without proper validation or authentication checks.
    Affected if The 'file' parameter can be controlled and the upload proceeds without validation errors or auth prompts
  5. Check access controls on sadmin
    Verify whether the sadmin directory is protected by authentication (e.g., .htaccess, web.config, or built-in CMS auth) or if it allows unauthenticated access.
    Affected if No authentication or IP-based restrictions are enforced on sadmin/fileedit.php
  6. Inspect uploaded file storage
    If file uploads are accepted, check if uploaded files are stored within the webroot and can be executed (e.g., .php files in a publicly accessible location).
    Affected if Uploaded files are stored in a web-accessible directory and can be executed directly

You are affected if UCMS version 1.6 is installed, the sadmin/fileedit.php file exists and is accessible, and the application accepts arbitrary file uploads through the 'file' parameter without authentication or proper validation.

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

Restrict access to the sadmin directory and disable the fileedit functionality until a patch is available. Implement proper file type validation, size limits, and store uploads outside webroot.

Fix this in Ucms Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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