EventonWordPress extension · Myeventon
CVE-2024-0233
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 · uneditedThe EventON WordPress plugin before 4.5.5, EventON WordPress plugin before 2.2.7 do not properly sanitise and escape a parameter before outputting it back in pages, leading to a Reflected Cross-Site Scripting which could be used against high privilege users such as admin
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 confidenceThe EventON WordPress plugin fails to properly sanitize and escape a user-supplied parameter before reflecting it back into the page output, creating a reflected Cross-Site Scripting (XSS) vulnerability. An attacker could craft a malicious URL containing JavaScript payload that, when clicked by a high-privilege administrator, would execute in their authenticated session.
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
< 2.2.7>= 4.0, < 4.5.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify EventON plugin is installedIn the WordPress admin dashboard, navigate to Plugins > Installed Plugins and locate 'EventON' or 'Myeventon Eventon' in the list of active pluginsAffected if The EventON plugin appears in the installed plugins list
-
Identify the installed EventON versionIn Plugins > Installed Plugins, find the EventON entry and record the version number displayed beneath the plugin nameAffected if Version is displayed and can be compared to affected ranges
-
Compare version against affected rangesCheck if the installed version is either below 2.2.7, or between 4.0 and 4.5.5 (>= 4.0 and < 4.5.5)Affected if Version is < 2.2.7 OR (version >= 4.0 AND version < 4.5.5)
You are affected if the EventON plugin is installed and its version is either below 2.2.7 or falls within the 4.0 to 4.5.5 range.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.2.74.5.5
Update EventON to version 4.5.5 or higher (or 2.2.7+ for the older branch), which includes proper sanitization and output escaping for the vulnerable parameter.
EventON version 2.2.7 or 4.5.5 (depending on your current major version branch)
- Backup your WordPress site before making any changes
- Identify your current EventON plugin version (check in WordPress admin > Plugins)
- If your version is < 2.2.7 (pre-4.0 versions), update EventON to version 2.2.7
- If your version is >= 4.0 but < 4.5.5, update EventON to version 4.5.5
- After update, verify the plugin functions correctly on your site
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
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 locallyCheck whether your project pulls in CVE-2024-0233 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-0233 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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