dbcve.org
EventonWordPress extension · Myeventon

CVE-2024-0238

MEDIUM · 6.1 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 →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Premium WordPress plugin before 4.5.6, EventON WordPress plugin before 2.2.8 do not have authorisation in an AJAX action, and does not ensure that the post to be updated belong to the plugin, allowing unauthenticated users to update arbitrary post metadata.

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 plugins (both Premium and standard versions) contain a broken access control vulnerability in an AJAX action that lacks proper authorization checks. This allows unauthenticated attackers to update arbitrary post metadata by exploiting the missing verification that the post belongs to the plugin.

MitigationUpdate EventON Premium to version 4.5.6 or later, and EventON standard to version 2.2.8 or later. If immediate update is not possible, implement custom authorization checks on the vulnerable 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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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 EventON plugin installation
    Locate the EventON plugin files in the WordPress wp-content/plugins directory, or use WordPress admin dashboard under Plugins to confirm EventON (or EventON Premium) is installed
    Affected if EventON or EventON Premium plugin is present on the WordPress site
  2. Determine installed EventON version
    Check the plugin header in the main EventON PHP file (usually eventon.php or class-evo-main.php) for the 'Version' defined constant, or view the plugin details in WordPress admin plugins list
    Affected if Version is below 2.2.7 OR version is 4.0 through 4.5.4 (inclusive)
  3. Verify AJAX endpoint accessibility
    Test access to the WordPress admin-ajax.php endpoint with the EventON-related AJAX action (typically involves a hook like 'evo_update_post_meta' or similar event-related action) without providing authentication credentials
    Affected if The AJAX endpoint responds successfully to unauthenticated requests without returning a permission error or requiring user authentication

A site is affected if EventON (standard or Premium) is installed with a version below 2.2.7 or between 4.0 and 4.5.4 inclusive, and the vulnerable AJAX action 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

Update EventON Premium to version 4.5.6 or later, and EventON standard to version 2.2.8 or later. If immediate update is not possible, implement custom authorization checks on the vulnerable AJAX endpoint.

Recommended fix High confidence

EventON (free) -> 2.2.8 or EventON Premium -> 4.5.6

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Identify whether you have EventON (free) or EventON Premium installed
  4. Check the currently installed version number of the plugin
  5. If version is < 2.2.7 (for free) or < 4.5.5 (for premium), navigate to Plugins > Add New > Upload or check for updates
  6. Update to version 2.2.8 (free) or 4.5.6 (premium)
  7. Verify the update was successful by confirming the new version number in Plugins list
  8. Test that the AJAX functionality works correctly after the update

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
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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