dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-41471

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
The Easy PayPal Events & Tickets plugin for WordPress before version 1.4 contains an information disclosure vulnerability in the QR code scanning endpoint that allows unauthenticated attackers to enumerate and retrieve all customer order records. Attackers can iterate over sequential WordPress post IDs through the scan_qr.php endpoint to harvest the complete set of orders stored in the database without requiring authentication or prior knowledge of specific order identifiers.

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 plugin for WordPress versions before 1.4 contains an unauthenticated information disclosure vulnerability in the scan_qr.php QR code scanning endpoint. Attackers can harvest all customer order records by iterating over sequential WordPress post IDs, exposing sensitive order data without authentication or prior knowledge of specific order identifiers.

MitigationUpgrade to version 1.4 or later which patches the vulnerability. Alternatively, implement proper authentication and authorization checks on the scan_qr.php endpoint to ensure only authorized users can access order data.

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. Verify plugin installation
    Check if the Easy PayPal Events & Tickets plugin is present in the WordPress plugins directory (wp-content/plugins/) or via WordPress admin plugin list
    Affected if Plugin is installed and active
  2. Identify installed version
    Read the plugin main file (e.g., easy-paypal-events-tickets.php) and locate the version comment/header, or check via WordPress admin plugin page
    Affected if Version is below 1.4 (e.g., 1.3.x, 1.2.x, etc.)
  3. Locate vulnerable endpoint file
    Check if scan_qr.php exists in the plugin directory path (wp-content/plugins/easy-paypal-events-tickets/scan_qr.php or similar path)
    Affected if scan_qr.php file exists in the plugin folder
  4. Confirm unauthenticated access vector
    Attempt a local HTTP request to the scan_qr.php endpoint (e.g., https://yoursite.com/wp-content/plugins/easy-paypal-events-tickets/scan_qr.php) without providing authentication cookies or credentials
    Affected if Endpoint returns order data or responds without requiring login (HTTP 200 instead of redirect to login)

User is affected if the plugin is installed with version below 1.4 AND the scan_qr.php file exists and is accessible without authentication.

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 1.4 or later which patches the vulnerability. Alternatively, implement proper authentication and authorization checks on the scan_qr.php endpoint to ensure only authorized users can access order data.

Recommended fix Moderate confidence

Easy PayPal Events & Tickets plugin version 1.4

  1. Update the Easy PayPal Events & Tickets WordPress plugin to version 1.4 or later via the WordPress admin dashboard under Plugins > All Plugins > Easy PayPal Events & Tickets > Update Now
  2. After updating, verify the plugin version displays as 1.4 or higher in the installed plugins list
  3. Confirm the scan_qr.php endpoint now properly enforces authorization before returning order data
  4. If immediate update is not possible, temporarily disable the scan_qr.php endpoint via .htaccess or web server configuration to block unauthenticated access

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