dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-6180

HIGH · 7.2 CVSS v3.1 Published 2024-07-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
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 plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'eventon_import_settings' ajax action in all versions up to, and including, 2.2.15. This makes it possible for unauthenticated attackers to update plugin settings, including adding stored cross-site scripting to settings options displayed on event calendar pages.

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 is vulnerable to unauthorized data modification due to a missing capability check on the 'eventon_import_settings' AJAX action. This allows unauthenticated attackers to update plugin settings and inject stored cross-site scripting (XSS) into event calendar page displays.

MitigationUpdate EventON to the latest version and add proper authorization checks (using check_ajax_referer and current_user_can) to the 'eventon_import_settings' AJAX action. Review and sanitize all settings that can be modified via AJAX.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Confirm EventON plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'EventON' or check the plugin files in /wp-content/plugins/eventon/ for the main PHP file to read the version header
    Affected if EventON plugin is not installed or not present in the WordPress environment
  2. Identify the installed EventON version
    Open the main EventON plugin file (usually eventon.php) and locate the Version header comment, or query the WordPress database options table for the 'eventon_version' option
    Affected if The installed version is unpatched and matches the vulnerable version range (prior to the fix in version 4.5.5)
  3. Locate the vulnerable AJAX action handler
    Search the EventON plugin files for 'eventon_import_settings' - typically in includes/class-ajax.php or similar AJAX handler files
    Affected if The 'eventon_import_settings' AJAX action is present in the codebase without proper capability checks
  4. Verify AJAX action lacks authorization
    Examine the PHP code for the eventon_import_settings action handler - check for missing check_ajax_referer() calls and absence of current_user_can() or similar capability checks before processing settings
    Affected if The AJAX handler executes without verifying user authentication or authorization (no current_user_can() check present)
  5. Test if settings can be modified without auth
    Send a POST request to /wp-admin/admin-ajax.php with action=eventon_import_settings and modified settings parameters (without valid nonce or authentication) using a tool like curl
    Affected if The AJAX endpoint accepts and processes the request without returning a 403 or requiring authentication

The environment is affected if EventON is installed with an unpatched version and the eventon_import_settings AJAX action accepts unauthenticated requests without capability verification, allowing settings modification and potential XSS injection.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update EventON to the latest version and add proper authorization checks (using check_ajax_referer and current_user_can) to the 'eventon_import_settings' AJAX action. Review and sanitize all settings that can be modified via AJAX.

Recommended fix Moderate confidence

EventON version 2.2.16 or latest available version

  1. Check the current version of the EventON plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate the EventON plugin and note the current version number
  4. If the installed version is 2.2.15 or lower, update the plugin to the latest available version
  5. After updating, verify the plugin settings have not been tampered with by navigating to EventON > Settings
  6. Review any unauthorized changes to settings, particularly around import/export functionality
  7. Consider reviewing user accounts for any unauthorized additions

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

Have this fixed 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 help mitigating

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-6180 — 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-6180 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