dbcve.org
EventonWordPress extension · Myeventon

CVE-2024-0236

MEDIUM · 5.3 CVSS v3.1 Published 2024-01-16
Fix available
A fix is available. Upgrade to 2.2.7 / 4.5.5 or later.
See remediation →
62/100
Remediation priority · Elevated
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
The EventON WordPress plugin before 4.5.5, EventON WordPress plugin before 2.2.7 do not have authorisation in an AJAX action, allowing unauthenticated users to retrieve the settings of arbitrary virtual events, including any meeting password set (for example for Zoom)

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 EventON WordPress plugin lacks proper authorization checks in an AJAX action, allowing unauthenticated users to access arbitrary virtual event configurations and retrieve sensitive settings including meeting passwords for integrations like Zoom.

MitigationUpdate EventON to version 4.5.5 (or 2.2.7 for older installations) to implement proper authorization validation on the affected AJAX endpoint.

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
EventonWordPress extension
Affected:< 2.2.7>= 4.0, < 4.5.5

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 checks

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

  1. Check installed EventON version
    Locate the main plugin file (eventon.php) in wp-content/plugins/eventon/ and read the version header comment, or query the WordPress database: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins' and check the plugin version via WP dashboard
    Affected if Version is less than 2.2.7, OR version is 4.0 through 4.5.4 (not including 4.5.5)
  2. Verify AJAX endpoint is exposed
    Test if the vulnerable AJAX action responds to unauthenticated requests. This typically involves sending a POST request to /wp-admin/admin-ajax.php with the specific eventON AJAX action name without including any authentication tokens
    Affected if The AJAX endpoint returns a valid response without requiring login credentials (HTTP 200 without 401/403)
  3. Inspect virtual event settings exposure
    If the AJAX endpoint is accessible, examine the response data for sensitive fields such as zoom_password, meeting_password, or similar integration credentials within event configuration data
    Affected if The response contains plaintext passwords or sensitive meeting credentials for Zoom or other integrations

You are affected if the installed EventON version falls below 2.2.7 or is between 4.0 and 4.5.4, and the vulnerable AJAX endpoint returns event configuration data including sensitive credentials without requiring authentication.

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 2.2.7 / 4.5.5 or later
Fixed in 2.2.74.5.5
Interim mitigation

Update EventON to version 4.5.5 (or 2.2.7 for older installations) to implement proper authorization validation on the affected AJAX endpoint.

Recommended fix Moderate confidence

EventON version 4.5.5 (or 2.2.7 for legacy 2.x branch)

  1. 1. Backup your WordPress site database and files before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in WordPress admin dashboard
  3. 3. Find EventON plugin in the list
  4. 4. If an update is available, click 'Update Now' to install version 4.5.5 or later
  5. 5. Alternatively, download EventON version 4.5.5 from a trusted source and upload via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the plugin version shows 4.5.5 or higher under Plugins > Installed Plugins
  7. 7. Test that unauthenticated users can no longer access event settings via AJAX
Caveat Review plugin settings after upgrade as minor layout changes may exist between 4.x versions; test any custom integrations using event data

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

Fix this in Eventon Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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