CVE-2018-12626
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/popup.php has XSS via the cat 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/popup.php via the cat parameter. The application fails to properly sanitize or validate user input before reflecting it back in the HTTP response, allowing an attacker to inject malicious JavaScript 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<= 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.
-
Confirm Eventum installation and versionLocate the Eventum installation directory and check the version file (typically version.php or similar in the root or includes directory). Common paths include /htdocs/ or the web root. Look for a version constant or variable.Affected if The installed version is 3.5.0 or any version lower than 3.5.0 (the vulnerable version range is <= 3.5.0)
-
Locate popup.php fileCheck if the file /htdocs/popup.php exists within the Eventum installation directory.Affected if The popup.php file exists and is accessible within the web document root
-
Identify the cat parameter handling in popup.phpOpen popup.php and locate the code that handles the 'cat' parameter. Search for $_GET['cat'] or $_REQUEST['cat'] and trace how this value is used in the response.Affected if The cat parameter is retrieved from user input and directly included in the HTML output without sanitization functions such as htmlspecialchars() or htmlentities()
-
Test for reflected XSS behaviorIf the application is in a testing environment, send a request to popup.php with a benign test value in the cat parameter (for example: cat=<script>alert(1)</script>) and verify whether the script tags are reflected unescaped in the response.Affected if The malicious payload is reflected directly in the HTTP response without HTML encoding, indicating the vulnerability is present and exploitable
The environment is affected if Eventum version 3.5.0 or lower is installed and the popup.php file reflects the cat parameter input without proper HTML 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 proper input validation and output encoding for the cat parameter in popup.php. Validate that input contains only expected characters (allowlist approach) and apply context-appropriate HTML encoding when reflecting user data in the response.
- 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-12626 — 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-12626 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