dbcve.org
EventumApplication · Eventum Project

CVE-2018-11569

CRITICAL · 9.8 CVSS v3.0 Published 2019-09-05
Fix available
A fix is available. Upgrade to 3.5.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Controller/ListController.php in Eventum 3.5.0 is vulnerable to Deserialization of Untrusted Data. Fixed in version 3.5.2.

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 confidence

Eventum 3.5.0 contains a deserialization vulnerability in Controller/ListController.php that allows attackers to deserialize untrusted data, potentially leading to remote code execution. This is caused by unsafe use of PHP's unserialize() function on user-controlled input without proper validation.

MitigationUpgrade to Eventum version 3.5.2 or later to apply the vendor patch that addresses the unsafe deserialization. If immediate upgrade is not possible, implement input validation and consider web application firewall rules.

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
EventumApplication
Affected:>= 3.5.0, < 3.5.2

CVSS 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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Eventum version
    Locate the version file or check the VERSION constant in the Eventum installation. Common locations include a VERSION file in the root directory, composer.json version field, or the config file. Run: grep -r "VERSION" --include="*.php" | head -20 to find version definitions.
    Affected if The installed version is 3.5.0, 3.5.1, or any version >= 3.5.0 and < 3.5.2.
  2. Locate the vulnerable ListController.php file
    Find the Controller/ListController.php file in the Eventum web root. Verify its existence and inspect the file for PHP's unserialize() function calls.
    Affected if The file exists and contains an unserialize() call operating on user-supplied input.
  3. Confirm the deserialization sink is reachable
    Examine the ListController.php code flow to determine if the unserialize() call processes data from $_GET, $_POST, or $_REQUEST superglobals without validation.
    Affected if The vulnerable deserialization code path can be triggered via HTTP requests without authentication or with standard user privileges.
  4. Check for indicators of exploitation
    Review web server access logs for patterns involving the ListController endpoint with serialized data payloads. Look for unusual PHP execution indicators in application logs.
    Affected if Logs show requests to the ListController containing serialized PHP objects or evidence of past exploitation attempts.

If the installed Eventum version is 3.5.0 or 3.5.1 (falling within >= 3.5.0 to < 3.5.2), the ListController.php file contains unsafe unserialize() usage on user input, and that endpoint is accessible, the environment is vulnerable to CVE-2018-11569.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 3.5.2 or later
Fixed in 3.5.2
Interim mitigation

Upgrade to Eventum version 3.5.2 or later to apply the vendor patch that addresses the unsafe deserialization. If immediate upgrade is not possible, implement input validation and consider web application firewall rules.

Recommended fix High confidence

3.5.2

  1. 1. Create a full backup of the Eventum installation directory and database before proceeding.
  2. 2. Download Eventum version 3.5.2 from the official Eventum repository or distribution source.
  3. 3. Extract the version 3.5.2 files and replace the existing installation files, preserving any local configuration files.
  4. 4. Run any database migration scripts if included in the 3.5.2 release.
  5. 5. Verify the Controller/ListController.php file has been updated to the patched version.
  6. 6. Test the application functionality to ensure normal operation.
  7. 7. Clear any application caches to ensure the new code is loaded.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Eventum Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-11569 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-11569 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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