CVE-2018-12622
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/ajax/update.php has XSS via the field_name 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 · moderate confidenceA reflected Cross-Site Scripting (XSS) vulnerability in Eventum 3.5.0 allows attackers to inject malicious scripts via the field_name parameter in htdocs/ajax/update.php. The unvalidated user input is directly reflected in the HTTP response without proper sanitization or output encoding.
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 identify the version. Typically found in a VERSION file, changelog, or the main application header. Check for files like VERSION, version.php, or a changelog file in the root or docs directory.Affected if The installed version is Eventum Project Eventum at version 3.5.0 or lower.
-
Verify affected file existsCheck if htdocs/ajax/update.php exists within the Eventum installation directory. This is the specific file referenced in the CVE as containing the vulnerable code.Affected if The file htdocs/ajax/update.php exists and is accessible via the web server.
-
Inspect field_name parameter handlingExamine the source code of htdocs/ajax/update.php and locate the code that handles the 'field_name' parameter from the HTTP request. Look for how this parameter is used and whether it is reflected in the HTTP response.Affected if The code retrieves the field_name parameter from user input (e.g., $_GET or $_POST) and directly includes it in the response without sanitization, encoding, or validation.
-
Test for reflected XSS in the responseSend a crafted HTTP request to htdocs/ajax/update.php with a test payload in the field_name parameter (e.g., field_name=<script>alert(1)</script>) and examine if the script tag appears unescaped in the response body.Affected if The injected script payload is reflected verbatim in the HTTP response without HTML entity encoding (e.g., <script> appears as <script>).
You are affected if you are running Eventum Project Eventum version 3.5.0 or lower and the htdocs/ajax/update.php file processes the field_name parameter without sanitization or output 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 input validation and output encoding for the field_name parameter; use context-appropriate escaping (HTML entity encoding) when reflecting user-supplied values in the response.
- Consultation1.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-12622 — 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-12622 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