dbcve.org
UlicmsApplication

CVE-2020-12703

MEDIUM · 6.1 CVSS v3.1 Published 2020-05-07
Fix available
A fix is available. Upgrade to 2020.2 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
UliCMS before 2020.2 has XSS during PackageController uninstall.

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

UliCMS before version 2020.2 contains a stored Cross-Site Scripting (XSS) vulnerability in the PackageController's uninstall functionality. The vulnerability allows malicious scripts to be injected through package uninstallation parameters, potentially executing in administrator browsers.

MitigationUpgrade UliCMS to version 2020.2 or later. Until upgrade, implement input validation and output encoding on all package management parameters.

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
UlicmsApplication
Affected:< 2020.2

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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 UliCMS installation
    Look for the UliCMS installation directory on the web server. Check for the presence of the main index.php file and the ulicms/ directory structure.
    Affected if UliCMS is not installed on the system.
  2. Determine installed UliCMS version
    Locate the version file or check the admin dashboard for the current UliCMS version number. The version is typically displayed in the admin panel footer or in a version.php file within the installation.
    Affected if The installed version is any version prior to 2020.2 (e.g., 2020.1, older releases).
  3. Verify PackageController module exists
    Check for the presence of the PackageController file in the UliCMS source code, typically found in the controller or similar directory structure.
    Affected if The PackageController file exists and is accessible via the web application.
  4. Confirm package management feature is accessible
    Log into the UliCMS administrator panel and navigate to the package management or modules section where uninstall functionality is available.
    Affected if The package management interface is accessible to authenticated administrators.

A system is affected if UliCMS version is confirmed to be below 2020.2 and the PackageController uninstall feature is accessible to administrators.

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
Upgrade available Upgrade to 2020.2 or later
Fixed in 2020.2
Interim mitigation

Upgrade UliCMS to version 2020.2 or later. Until upgrade, implement input validation and output encoding on all package management parameters.

Fix this in Ulicms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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