CVE-2020-12704
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 · uneditedUliCMS before 2020.2 has PageController stored XSS.
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 confidenceUliCMS before version 2020.2 contains a stored cross-site scripting (XSS) vulnerability in the PageController component. The vulnerability allows attackers to inject malicious JavaScript code that gets permanently stored and executed when other users view the affected page content.
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< 2020.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed UliCMS versionLocate the version file or check the admin dashboard under System > Info or similar. Common locations include a version.php file, README, or the footer of the admin panel.Affected if The version number is lower than 2020.2 (e.g., 2020.1, older releases)
-
Confirm PageController is accessibleVerify that the PageController component is active by accessing pages or checking the /?controller=page or similar URL path if the application uses query-based routing.Affected if The PageController handles page content rendering and is reachable in the application
-
Examine page content for injected scriptsInspect the database tables storing page content (typically pages, content, or similar tables) or view the HTML source of published pages to look for unexpected script tags, javascript: URIs, or event handlers like onload/onerror.Affected if Page content contains unsanitized script tags or JavaScript event attributes that would execute in a user's browser
-
Check recent content changesReview content editing logs or the database for recent entries in page content fields that contain <script>, <img onerror>, <svg onload>, or similar payloads.Affected if Any page content entries contain JavaScript code that was not intentionally added by an administrator
You are affected if your UliCMS installation is version 2020.1 or earlier and the PageController is used to render page content that may contain malicious scripts.
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 data2020.2
Upgrade UliCMS to version 2020.2 or later, which contains the fix for this stored XSS vulnerability in PageController.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-12704 — 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-12704 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