dbcve.org
EventonWordPress extension · Myeventon

CVE-2024-0235

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 email addresses of any users on the blog

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 before versions 4.5.5 and 2.2.7 lacks proper authorization checks in an AJAX action, allowing unauthenticated attackers to query and retrieve email addresses of any registered users on the WordPress site.

MitigationUpgrade EventON to version 4.5.5 (or 2.2.7 for older branch) to include the vendor patch that adds proper authorization validation to 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. Confirm EventON plugin is installed
    Access WordPress admin panel and navigate to Plugins > Installed Plugins, or check the /wp-content/plugins/ directory for eventon or myeventon folders
    Affected if EventON plugin is present in the WordPress installation
  2. Identify installed EventON version
    In WordPress admin, go to Plugins > Installed Plugins and locate the version number displayed for EventON, or read the Version header in the main plugin PHP file (eventon.php or class-evon-main.php)
    Affected if Version is less than 2.2.7 OR version is 4.0.x through 4.5.4 (the vulnerable version range)
  3. Check if public AJAX user query is possible
    Identify the plugin AJAX endpoints (typically in /includes/ajax/ folder or registered via wp_ajax_ hooks) and test if unauthenticated requests can query user data. Use a tool like Burp Suite or curl to send requests to the AJAX action without authentication cookies
    Affected if The AJAX endpoint responds to unauthenticated requests and returns email addresses from the WordPress user database

The environment is affected if EventON plugin is installed with a version less than 2.2.7, or with version 4.0.x through 4.5.4, and the vulnerable AJAX endpoint is accessible without 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

Upgrade EventON to version 4.5.5 (or 2.2.7 for older branch) to include the vendor patch that adds proper authorization validation to the affected AJAX endpoint.

Recommended fix High confidence

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

  1. Backup your WordPress site before making any changes
  2. Identify which version branch of EventON you are currently using (2.x or 4.x)
  3. If using EventON version 1.x or 2.x: Update the plugin to version 2.2.7
  4. If using EventON version 4.x: Update the plugin to version 4.5.5
  5. Navigate to Plugins > Installed Plugins in WordPress admin
  6. Locate EventON and click Update Now
  7. After update completes, verify the new version number in the plugins list
  8. Confirm the AJAX action is no longer accessible to unauthenticated users

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

Fix this in Eventon 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-0235 — 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-0235 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