dbcve.org
Event MonsterWordPress extension · Awplife

CVE-2024-1895

HIGH · 7.5 CVSS v3.1 Published 2024-04-30
Fix available
A fix is available. Upgrade to 1.4.0 or later.
See remediation →
81/100
Remediation priority · High
Remotely reachable 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
The Event Monster – Event Management, Tickets Booking, Upcoming Event plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.3.9 via deserialization via shortcode of untrusted input from a custom meta value. This makes it possible for authenticated attackers, with contributor access and above, to inject a PHP Object. No POP chain is present in the vulnerable plugin. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code.

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

The Event Monster WordPress plugin versions up to 1.3.9 is vulnerable to PHP Object Injection via deserialization of untrusted input from custom meta values through a shortcode. Authenticated attackers with contributor-level access or higher can inject arbitrary PHP objects. While no POP chain exists within the plugin itself, additional plugins or themes on the target system that provide a POP chain could enable remote code execution, arbitrary file deletion, or sensitive data retrieval.

MitigationUpdate the Event Monster plugin to a version beyond 1.3.9. Additionally, audit installed plugins and themes for POP chain capabilities and remove any that could be exploited in conjunction with this vulnerability.

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
Event MonsterWordPress extension
Affected:< 1.4.0

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/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. Verify Event Monster plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Event Monster' by Awplife, or check the filesystem at wp-content/plugins/ for event-monster or similar plugin directory
    Affected if The plugin is present on the WordPress site
  2. Determine installed plugin version
    In WordPress admin plugins list, find the version number listed under the Event Monster plugin, or read the main plugin PHP file header for 'Version:' value
    Affected if Version is 1.3.9 or lower (any version below 1.4.0)
  3. Identify if shortcode functionality is accessible
    Check if the plugin provides a shortcode (commonly [event_monster] or similar) by reviewing plugin documentation or searching plugin files for add_shortcode function calls; test if shortcode renders on any page
    Affected if The shortcode is present and can be rendered by authenticated users
  4. Confirm contributor-level or higher user accounts exist
    In WordPress admin, go to Users > All Users and identify any users with Contributor, Author, Editor, or Administrator roles
    Affected if At least one user with contributor-level or higher access exists on the site
  5. Review custom meta values associated with events
    Check WordPress post meta tables (wp_postmeta) for meta keys related to event monster plugin, or examine the database for any serialized data in custom fields linked to event posts
    Affected if Custom meta values with serialized data exist and can be modified by authenticated users

A site is affected if it runs Event Monster plugin version 1.3.9 or below, has the plugin shortcode enabled, and has at least one contributor-level user account with ability to modify event-related custom meta values.

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 1.4.0 or later
Fixed in 1.4.0
Interim mitigation

Update the Event Monster plugin to a version beyond 1.3.9. Additionally, audit installed plugins and themes for POP chain capabilities and remove any that could be exploited in conjunction with this vulnerability.

Recommended fix High confidence

1.4.0

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'Event Monster – Event Management, Tickets Booking, Upcoming Event' plugin
  4. If an update is available, click 'Update Now' to update to version 1.4.0
  5. Alternatively, download version 1.4.0 from the WordPress Plugin Repository and upload it manually via Plugins > Add New > Upload Plugin
  6. After updating, verify the plugin version is showing 1.4.0

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

Fix this in Event Monster Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1895 — 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-2024-1895 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