dbcve.org
EventonWordPress extension · Myeventon

CVE-2024-0237

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 through 4.5.8, EventON WordPress plugin before 2.2.7 do not have authorisation in some AJAX actions, allowing unauthenticated users to update virtual events settings, such as meeting URL, moderator, access details etc

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 on certain AJAX actions, enabling unauthenticated attackers to modify virtual event settings including meeting URLs, moderator credentials, and access details. This is a broken access control vulnerability where AJAX endpoints do not verify user permissions before allowing configuration changes.

MitigationUpdate EventON plugin to version 2.2.7 or later which implements proper authorization checks on AJAX actions. Until patched, monitor for unauthorized modifications to event settings.

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

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

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

  1. Identify installed EventON version
    In WordPress admin, go to Plugins > Installed Plugins and find EventON. The version number is displayed under the plugin name. Alternatively, check the main plugin file (eventon.php) for the 'Version:' header comment.
    Affected if The installed version is less than 2.2.7, OR the version is 4.0.x through 4.5.4.
  2. Verify AJAX endpoint accessibility
    Test whether the EventON AJAX actions are reachable without authentication. The vulnerable endpoints typically respond to wp-admin/admin-ajax.php with action names containing 'evo-ao' or similar eventON prefixes. Use a tool like curl to send a request to these endpoints without providing authentication tokens.
    Affected if The AJAX endpoints respond with success or allow configuration changes without requiring a logged-in session or capability check.
  3. Inspect event post meta for changes
    In WordPress database (wp_postmeta table), query for posts where post_type is 'ajde_events' or similar eventON custom post types. Review the meta_key values related to meeting URLs (often 'evo_hide_otter'), moderator credentials, and access details. Check for unexpected values or recent modifications.
    Affected if Event meta values have been modified to unfamiliar meeting URLs, credentials, or access settings that were not intentionally changed by authorized administrators.
  4. Review AJAX action logs for EventON calls
    Check server access logs for requests to /wp-admin/admin-ajax.php that include EventON-related action parameters. Look for requests lacking WP session cookies or nonces that still returned successful responses.
    Affected if Logs show successful AJAX requests to EventON endpoints from IP addresses not associated with logged-in administrators.

Your environment is affected if the EventON plugin version is below 2.2.7 (for the 2.x branch) or between 4.0 and 4.5.4 (for the 4.x branch), and the AJAX endpoints are accessible without authentication or show unauthorized event modifications.

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 plugin to version 2.2.7 or later which implements proper authorization checks on AJAX actions. Until patched, monitor for unauthorized modifications to event settings.

Recommended fix High confidence

EventON 2.2.7 (for 2.x branch) or EventON 4.5.5 (for 4.x branch)

  1. Backup your WordPress site database and files before making any changes
  2. Navigate to Plugins > Installed Plugins in WordPress admin dashboard
  3. Locate the EventON plugin
  4. If using version 2.x, update to version 2.2.7 or later
  5. If using version 4.x, update to version 4.5.5 or later
  6. Verify the plugin update completed successfully
  7. Test that AJAX actions related to virtual events now require proper authorization
  8. Confirm virtual event settings can only be modified by authenticated users with appropriate permissions
Caveat Minor plugin updates typically do not introduce breaking changes; test in staging if available

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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