dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-14657

HIGH · 7.2 CVSS v3.1 Published 2026-01-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 Eventin – Event Manager, Events Calendar, Event Tickets and Registrations plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'post_settings' function in all versions up to, and including, 4.0.51. This makes it possible for unauthenticated attackers to modify plugin settings. Furthermore, due to insufficient input sanitization and output escaping on the 'etn_primary_color' setting, this enables unauthenticated attackers to inject arbitrary web scripts that will execute whenever a user accesses a page where Eventin styles are loaded.

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 Eventin WordPress plugin versions up to 4.0.51 lacks a capability check on the post_settings function, allowing unauthenticated attackers to modify plugin settings. Additionally, the etn_primary_color setting has insufficient input sanitization and output escaping, enabling stored XSS injection that executes when pages load Eventin styles.

MitigationUpdate the Eventin plugin to the latest version beyond 4.0.51, which should include proper capability authorization checks and correct sanitization/escaping for the etn_primary_color setting.

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. Verify Eventin plugin is installed
    Check the WordPress plugins directory for the Eventin plugin folder (commonly 'eventin' or 'wpeventin') or query the wp_plugins database table for the plugin name
    Affected if Eventin plugin is present in the WordPress installation
  2. Check installed Eventin version
    Read the main plugin file header (e.g., eventin.php) to find the 'Version' tag, or query wp_postmeta or plugin files for the version number
    Affected if Version is 4.0.51 or lower
  3. Verify post_settings function exposure
    Check if the WordPress REST API endpoint for post_settings is accessible without authentication, or inspect the plugin source code for the function and its capability checks
    Affected if post_settings function can be called by unauthenticated users (no current_user_check or capability verification present)
  4. Check etn_primary_color setting existence
    Query the wp_options table for the option_name 'etn_primary_color' or inspect saved Eventin settings in the database
    Affected if etn_primary_color option exists with a user-supplied value that may contain unsanitized content

The environment is affected if Eventin plugin versions 4.0.51 or lower are installed and the vulnerable post_settings function or etn_primary_color setting is exposed to unauthenticated users.

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 the Eventin plugin to the latest version beyond 4.0.51, which should include proper capability authorization checks and correct sanitization/escaping for the etn_primary_color setting.

Recommended fix Moderate confidence

Version 4.0.52 or later

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the Eventin plugin
  4. Check if an update is available and update to version 4.0.52 or higher
  5. If no update is shown, manually download the latest version from wordpress.org/plugins/eventin/ and reinstall

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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