dbcve.org
EventinWordPress extension · Themewinter

CVE-2025-1766

MEDIUM · 5.3 CVSS v3.1 Published 2025-03-20
Fix available
A fix is available. Upgrade to 4.0.25 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 Event Manager, Events Calendar, Tickets, Registrations – Eventin plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'payment_complete' function in all versions up to, and including, 4.0.24. This makes it possible for unauthenticated attackers to update the status of ticket payments to 'completed', possibly resulting in financial loss.

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 has a Broken Access Control vulnerability where the 'payment_complete' function lacks a capability check, allowing unauthenticated attackers to arbitrarily update ticket payment statuses to 'completed' by manipulating the payment status via the vulnerable function.

MitigationUpdate to version 4.0.25 or later which includes proper capability checks. If immediate update is not possible, implement server-side validation to verify payment completion through the payment gateway before trusting status updates.

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
EventinWordPress extension
Affected:< 4.0.25

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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
    Navigate to WordPress admin > Plugins and confirm if the Eventin plugin by Themewinter is installed and active
    Affected if Eventin plugin is present and active in the WordPress installation
  2. Check installed Eventin version
    In WordPress admin > Plugins, locate Eventin and note the version number. Compare your version against 4.0.25
    Affected if The installed version is lower than 4.0.25 (e.g., 4.0.24, 4.0.20, etc.)
  3. Examine payment_complete function for capability check
    Access the plugin source code and locate the payment_complete function. Inspect whether the function includes a capability check such as current_user_can() before processing payment status updates
    Affected if The payment_complete function lacks a capability check and allows execution without authentication
  4. Check payment status update accessibility
    Test whether the payment status update endpoint/function can be accessed without authentication by examining the function's permission_callback or checking if the function is hooked to a publicly accessible action
    Affected if The payment status update functionality is accessible to unauthenticated users

You are affected if Eventin plugin is installed with a version lower than 4.0.25 and the payment_complete function lacks proper capability verification, allowing unauthenticated status changes.

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 4.0.25 or later
Fixed in 4.0.25
Interim mitigation

Update to version 4.0.25 or later which includes proper capability checks. If immediate update is not possible, implement server-side validation to verify payment completion through the payment gateway before trusting status updates.

Recommended fix High confidence

4.0.25

  1. 1. Backup your WordPress database and files before making any changes.
  2. 2. Navigate to the WordPress admin dashboard > Plugins > Installed Plugins.
  3. 3. Find the Eventin plugin in the list.
  4. 4. If an update is available, click 'Update Now' to upgrade to version 4.0.25 or later.
  5. 5. Alternatively, download version 4.0.25 from the WordPress plugin repository and upload it manually via Plugins > Add New > Upload Plugin.
  6. 6. After updating, verify the plugin version shows 4.0.25 or higher in the installed plugins list.

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

Fix this in Eventin Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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