CVE-2018-16761
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 · uneditedEventum before 3.4.0 has an open redirect vulnerability.
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 confidenceEventum before version 3.4.0 contains an open redirect vulnerability. Attackers can manipulate URL parameters to redirect users to malicious external sites, potentially facilitating phishing attacks. The CVSS 6.1 score reflects the medium severity of this input validation issue.
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.4.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 installation directorySearch for Eventum files on the system. Common locations include /var/www/html/, /opt/, or the web server document root. Look for directories containing 'eventum' in the name or check for config files like 'config.php' with Eventum-specific settings.Affected if Eventum software is found on the system
-
Identify installed Eventum versionCheck the version file or changelog. Common paths include: VERSION, VERSION.txt, changelog.txt, or the main config/settings file. Look for a version string or number within the files.Affected if The version cannot be determined or is found to be below 3.4.0
-
Verify vulnerable URL redirect functionality is accessibleExamine the application for URL parameter handling that performs redirects. Check scripts that process 'redirect', 'url', 'goto', or similar parameters. Look for code using header(), header('Location: ...'), or similar redirect functions that accept user-controlled input.Affected if The application contains redirect logic that accepts URL parameters without proper validation
-
Confirm affected version against CVE scopeCompare the identified version number to the affected range: Eventum versions before 3.4.0. Review release notes or changelog to confirm the exact version installed.Affected if Installed version is earlier than 3.4.0
The environment is affected if Eventum is installed with a version number lower than 3.4.0 and the application processes redirect URL parameters without validation.
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 data3.4.0
Upgrade Eventum to version 3.4.0 or later to obtain the patch for this open redirect vulnerability.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-16761 — 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-16761 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