dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-13039

MEDIUM · 5.3 CVSS v3.1 Published 2026-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 6 weeks old

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 Calendar, Event Registration, Tickets & Booking (AI Powered) plugin for WordPress is vulnerable to authorization bypass due to a regression in versions from 4.0.26 up to and including 4.1.15. This is due to the plugin not properly verifying that a user is authorized to perform an action in the payment_complete() function of PaymentController.php. This makes it possible for unauthenticated attackers to mark unpaid ticket orders as completed by submitting a fabricated SureCart checkout ID or FluentCart cart hash, granting themselves paid event access, QR-code attendee tickets, and order confirmation emails without making any real payment. The wp_rest nonce required to reach the vulnerable endpoint is embedded in every public event page, meaning no WordPress session or credentials are needed to obtain it. This vulnerability represents a regression — the same function and endpoint were previously patched but the fix did not persist through subsequent releases.

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 plugin for WordPress contains an authorization bypass in the payment_complete() function of PaymentController.php in versions 4.0.26 through 4.1.15. Unauthenticated attackers can mark unpaid ticket orders as complete by submitting fabricated SureCart checkout IDs or FluentCart cart hashes, bypassing the wp_rest nonce verification which is publicly exposed on event pages. This grants paid event access, QR-code tickets, and order confirmations without payment.

MitigationUpgrade to version 4.1.16 or later which contains the regression fix, or implement proper user authorization verification in the payment_complete() function to validate that the requester owns the order before marking it complete.

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
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. Check Eventin plugin version installed
    Navigate to WordPress admin > Plugins > Installed Plugins > Eventin, or check the plugin header in eventin/eventin.php for the Version constant
    Affected if version is between 4.0.26 and 4.1.15 inclusive
  2. Verify payment functionality is in use
    Check if the site uses SureCart or FluentCart for event ticket payments by reviewing active plugins and Eventin payment settings
    Affected if payment processing through SureCart or FluentCart is enabled on the site
  3. Inspect payment_complete endpoint exposure
    Review the PaymentController.php file in the plugin to confirm the payment_complete() function lacks proper authorization checks on the wp_rest nonce validation
    Affected if the payment_complete function accepts requests without validating user ownership of the order
  4. Check public nonce exposure
    Examine event pages to determine if wp_rest nonces are exposed in publicly accessible HTML (check page source for event-related REST API nonce fields)
    Affected if wp_rest nonces are visible in the source of public event pages

You are affected if the Eventin plugin version is 4.0.26 through 4.1.15 and the site uses SureCart or FluentCart for payment processing with the vulnerable payment_complete endpoint publicly accessible.

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

Upgrade to version 4.1.16 or later which contains the regression fix, or implement proper user authorization verification in the payment_complete() function to validate that the requester owns the order before marking it complete.

Recommended fix Moderate confidence

Latest version available in WordPress plugin repository (version > 4.1.15)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Eventin – Event Calendar, Event Registration, Tickets & Booking (AI Powered)' plugin
  4. 4. Check the current installed version (should be between 4.0.26 and 4.1.15 inclusive)
  5. 5. If an update is available, update to the latest version available from the WordPress plugin repository
  6. 6. Verify the update was successful and the new version is greater than 4.1.15

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-2026-13039 — 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-2026-13039 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