Tickera < 3.5.2.5 - Ticket leakage through IDOR

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

• tickera tickerabefore 3.5.2.5

Versions reported by the vendor

Affected version ranges reported by the assigning authority (WPScan). Independent of NVD's CPE analysis and usually ahead of it.

• Unknown Tickera

  • before 3.5.2.5affected · semver

Other highest-scoring records for the same primary product.

• CVE-2026-82226WordPress Tickera plugin <= 3.6.0.2 - PHP Object Injection vulnerability
  39Monitor
• CVE-2026-105889WordPress Tickera plugin <= 3.6.0.6 - SQL Injection vulnerability
  37Monitor
• CVE-2024-35729WordPress Tickera plugin <= 3.5.2.6 - Broken Access Control vulnerability
  35Monitor
• CVE-2024-10263Tickera – WordPress Event Ticketing <= 3.5.4.4 - Unauthenticated Arbitrary Shortcode Execution
  29Monitor
• CVE-2025-67939WordPress Tickera plugin <= 3.5.6.2 - Broken Access Control vulnerability
  26Monitor
• CVE-2021-24797Tickera < 3.4.8.3 - Unauthenticated Stored Cross-Site Scripting
  24Monitor

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Root cause

The endpoint fetches the record by the ID sent in the request, but never checks whether the record belongs to the requesting user.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

1const invoice = await Invoice.findById(req.params.id);2res.json(invoice);

1const invoice = await Invoice.findOne({2  id: req.params.id,3  ownerId: req.user.id,4});5if (!invoice) return res.sendStatus(404);6res.json(invoice);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.