CVE-2018-11473
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 · uneditedMonstra CMS 3.0.4 has XSS in the registration Form (i.e., the login parameter to users/registration).
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 confidenceMonstra CMS 3.0.4 contains a cross-site scripting (XSS) vulnerability in the user registration form. The login parameter submitted to users/registration is not properly sanitized, allowing an attacker to inject malicious JavaScript code that executes in the browsers of other users who view the registration data.
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= 3.0.4CVSS 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.0/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.
-
Confirm Monstra CMS installationLook for characteristic Monstra CMS files such as index.php in the web root, or the /monstra/ directory containing the admin panel. Check for folders like /users/, /plugins/, /themes/.Affected if Monstra CMS files are present in the web directory
-
Identify installed versionExamine the version file or source code. In Monstra CMS, check the system/bootstrap.php or similar core files for a version constant, or look for a version.php file. Alternatively, check the admin dashboard footer for the version number.Affected if The installed version is exactly 3.0.4
-
Verify registration feature is accessibleAttempt to access the registration form at /users/registration or /index.php?route=users/registration on your site. Confirm the page loads and displays the login input field.Affected if The registration form is publicly accessible and includes a login/username input field
-
Confirm vulnerability contextThe vulnerability exists specifically in the login parameter submitted to the registration form. If you are on version 3.0.4 and the registration form is accessible, the login field is not properly sanitized before being stored and displayed.Affected if Both conditions are true: version is 3.0.4 AND registration functionality is enabled and accessible
You are affected if Monstra CMS version 3.0.4 is installed and the user registration feature is enabled and accessible on your server.
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 proper input validation and output encoding on all user-supplied input in the registration form, specifically the login parameter. Use context-appropriate escaping and consider implementing a content security policy as defense-in-depth.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-11473 — 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-2018-11473 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