dbcve.org
Hard-coded CredentialsWeakness · CWE-798

CVE-2026-32834

HIGH · 7.5 CVSS v3.1 Published 2026-05-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/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
Easy PayPal Events & Tickets plugin for WordPress before version 1.4 contains a hardcoded authentication bypass vulnerability in the QR code scanning functionality that allows unauthenticated remote attackers to bypass hash verification by supplying 'test' as the hash parameter. Attackers can access the vulnerable endpoint via the add_wpeevent_button_qr action to retrieve sensitive order details including PayPal transaction IDs, customer email addresses, purchase amounts, and ticket information for any order with a known or guessed post ID.

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 Easy PayPal Events & Tickets WordPress plugin before v1.4 contains a hardcoded authentication bypass in its QR code scanning functionality. The add_wpeevent_button_qr endpoint accepts 'test' as a valid hash parameter, bypassing actual hash verification and allowing unauthenticated access to order details including PayPal transaction IDs, customer emails, purchase amounts, and ticket information by supplying known or guessed post IDs.

MitigationUpdate the Easy PayPal Events & Tickets plugin to version 1.4 or later to receive the patched code that removes the hardcoded 'test' hash bypass.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 Easy PayPal Events & Tickets plugin is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or inspect /wp-content/plugins/ directory for the easy-paypal-events-tickets folder
    Affected if The plugin folder exists in the WordPress installation
  2. Identify installed plugin version
    In WordPress adminPlugins list, locate Easy PayPal Events & Tickets and read the version number under the plugin name; alternatively, check the main plugin file header in /wp-content/plugins/easy-paypal-events-tickets/
    Affected if Version is lower than 1.4 or cannot be determined (assume affected)
  3. Verify vulnerable endpoint exists
    Make a GET request to /wp-admin/admin-ajax.php?action=add_wpeevent_button_qr with a test post ID parameter; check if the endpoint responds (no authentication required)
    Affected if Endpoint responds without requiring authentication
  4. Test hardcoded hash bypass
    Send a request to the vulnerable endpoint with hash=test and a valid post_id parameter (e.g., ?action=add_wpeevent_button_qr&post_id=1&hash=test); inspect response for order details
    Affected if Response returns PayPal transaction IDs, customer emails, or ticket data without a valid hash verification

If the plugin is installed with version below 1.4 and the QR scanning endpoint responds to unauthenticated requests using hash=test, the environment is affected by this authentication bypass.

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 Easy PayPal Events & Tickets plugin to version 1.4 or later to receive the patched code that removes the hardcoded 'test' hash bypass.

Recommended fix High confidence

1.4

  1. Backup your WordPress site and database before making any changes.
  2. Navigate to the WordPress admin dashboard and go to Plugins > All Plugins.
  3. Locate the 'Easy PayPal Events & Tickets' plugin in the list.
  4. Click 'Update now' on the plugin to install version 1.4 (or the latest stable version).
  5. Alternatively, use WP-CLI: `wp plugin install easy-paypal-events-tickets --version=1.4 --force` (or the latest version).
  6. After updating, verify the installed version is 1.4 or higher in the Plugins list.
  7. Test the QR code scanning functionality to confirm the hardcoded credential is no longer present.

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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