CVE-2018-12623
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/switch.php has XSS via the current_page 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 confidenceEventum 3.5.0 contains a reflected Cross-Site Scripting (XSS) vulnerability in htdocs/switch.php. The current_page parameter is not properly sanitized before being reflected back in the HTML output, allowing an attacker to inject malicious JavaScript code that executes in 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<= 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.
-
Identify Eventum installationLocate the Eventum installation directory. Check for files like config.php or known Eventum directories (htdocs, lib, etc.)Affected if The application is Eventum Project Eventum
-
Determine Eventum versionCheck for a version file or examine the source code for version strings. Common locations include a VERSION file, config files, or the main index.php header commentsAffected if The installed version is 3.5.0 or any version lower than 3.5.0
-
Locate vulnerable fileCheck if htdocs/switch.php exists in the installation directoryAffected if The file htdocs/switch.php is present in the Eventum installation
-
Verify current_page parameter handlingExamine the source code of htdocs/switch.php to see if the current_page parameter is used and reflected in HTML output without proper sanitization or encodingAffected if The current_page parameter is echoed back in HTML without sanitization (e.g., no htmlspecialchars or equivalent encoding)
-
Test for XSS vulnerabilitySubmit a test payload in the current_page parameter (e.g., current_page=<script>alert(1)</script>) via a GET request to switch.php and observe if the script tag is reflected unescaped in the responseAffected if The malicious payload is reflected in the HTML output without encoding
You are affected if you are running Eventum version 3.5.0 or lower and the htdocs/switch.php file is accessible with the current_page parameter being reflected without sanitization.
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 dataSanitize and validate the current_page parameter using output encoding before reflecting it in HTML. Implement allowlist-based validation for the parameter and ensure all user-supplied data is properly escaped using context-appropriate encoding.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-12623 — 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-12623 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