CVE-2019-18219
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 · uneditedSitemagic CMS 4.4.1 is affected by a Cross-Site-Scripting (XSS) vulnerability, as it fails to validate user input. The affected components (index.php, upgrade.php) allow for JavaScript injection within both GET or POST requests, via a crafted URL or via the UpgradeMode POST parameter.
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 confidenceSitemagic CMS 4.4.1 contains a reflected Cross-Site-Scripting vulnerability in index.php and upgrade.php. The application fails to properly validate or sanitize user-supplied input in both GET parameters (via crafted URLs) and POST parameters (UpgradeMode), allowing injection of arbitrary JavaScript code that executes in the context of the victim's browser.
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= 4.4.1CVSS 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 Sitemagic CMS installationLocate the Sitemagic installation directory and check for version file or footer metadata. Common paths include the web root or /cms/ subdirectory. Look for version information in footer, README, or metadata files.Affected if Sitemagic CMS is installed and the version cannot be determined or shows 4.4.1
-
Verify installed version is 4.4.1Access the version file or admin panel to confirm the exact version number. Compare against the affected version 4.4.1.Affected if The installed version is exactly 4.4.1
-
Confirm index.php endpoint is accessibleAccess the site's index.php page. Examine the HTTP response and URL parameters. Test by submitting a benign test string (such as <script>alert(1)</script>) in the URL query string and observe if it is reflected unescaped in the response HTML.Affected if User-supplied input in the URL is reflected in the response without HTML entity encoding
-
Confirm upgrade.php endpoint is accessibleLocate and access the upgrade.php file within the Sitemagic installation. Inspect the UpgradeMode POST parameter handling. Submit a test payload in the UpgradeMode parameter and verify if the input is reflected without sanitization in the response.Affected if The UpgradeMode POST parameter value is reflected in the response without proper sanitization
A system is affected if it runs Sitemagic CMS version 4.4.1 AND has accessible index.php or upgrade.php endpoints where user input is reflected without HTML entity encoding.
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 dataImplement robust input validation and output encoding for all user-supplied data in index.php and upgrade.php. Apply context-appropriate sanitization (e.g., HTML entity encoding) before reflecting any user input in HTTP responses.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-18219 — 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-2019-18219 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