CVE-2020-19158
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 · uneditedCross Site Scripting (XSS) in S-CMS build 20191014 and earlier allows remote attackers to execute arbitrary code via the 'Site Title' parameter of the component '/data/admin/#/app/config/'.
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 confidenceReflected XSS vulnerability in S-CMS admin panel at /data/admin/#/app/config/ where the 'Site Title' parameter is not properly sanitized before being rendered in the admin interface, allowing injection of malicious JavaScript that executes in the browser of administrators viewing the configuration page.
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= 2019-10-14CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm S-CMS installationIdentify if S-CMS is running in your environment by checking for the S-CMS admin panel or its characteristic file structureAffected if S-CMS is installed and accessible on the system
-
Identify installed S-CMS versionLocate the version identifier for your S-CMS installation, typically found in system files, changelogs, or the admin dashboard about pageAffected if The installed version matches 2019-10-14 exactly
-
Verify admin panel accessibilityConfirm the admin panel at /data/admin/ is reachable and requires authenticationAffected if The admin panel is accessible and accepts administrator credentials
-
Locate the config moduleNavigate to the configuration page at /data/admin/#/app/config/ or its equivalent in your S-CMS admin interfaceAffected if The Site Title configuration field is present and editable
-
Inspect Site Title output handlingExamine the source code or template files that render the Site Title parameter in the admin interface to determine if output encoding or sanitization is appliedAffected if The Site Title value is rendered without proper encoding or sanitization, allowing script injection
You are affected if S-CMS version 2019-10-14 is installed, the admin panel is accessible, and the Site Title parameter is rendered without output encoding in the configuration page.
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 dataApply output encoding/sanitization to the Site Title parameter when rendered in the admin interface, or upgrade to a patched version of S-CMS if available. Input validation should also be implemented.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2020-19158 — 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-2020-19158 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