CVE-2018-12627
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 · uneditedAn issue was discovered in Eventum 3.5.0. /htdocs/list.php has XSS via the show_notification_list_issues or show_authorized_issues 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 confidenceCross-site scripting (XSS) vulnerability in Eventum 3.5.0's /htdocs/list.php allows injection of malicious script through the show_notification_list_issues or show_authorized_issues parameters. User-supplied input in these parameters is reflected back without proper sanitization, enabling an attacker to execute arbitrary JavaScript in the context of a 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<= 3.5.0CVSS 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.
-
Locate Eventum installationSearch for the Eventum installation directory, typically in web root paths like /var/www/html/, /htdocs/, or check your web server document root for an 'eventum' folder or the presence of list.phpAffected if Eventum is installed and accessible via web
-
Identify Eventum versionCheck for a version file in the Eventum directory, commonly found as VERSION, config.php, or in the /htdocs/ directory. Look for a version identifier such as '3.5.0' or check the source code for a version constantAffected if Installed version is 3.5.0 or any version <= 3.5.0
-
Verify list.php exists and is accessibleConfirm the file /htdocs/list.php exists in the Eventum installation directory and is accessible via the web serverAffected if list.php file exists and responds to HTTP requests
-
Check for lack of input sanitization in list.phpExamine the source code of list.php, specifically looking at how the show_notification_list_issues and show_authorized_issues parameters are handled. Search for instances where these parameters are directly echoed or reflected back without htmlspecialchars() or equivalent encodingAffected if The parameters are reflected in the output without proper HTML encoding or sanitization
If Eventum version 3.5.0 or lower is installed and list.php reflects the show_notification_list_issues or show_authorized_issues parameters without sanitization, the environment is affected by this XSS vulnerability.
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 input validation and output encoding for the affected parameters in list.php. Use context-appropriate escaping functions (such as htmlspecialchars in PHP) when reflecting user input back to the browser.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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 $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-12627 — 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-12627 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