CVE-2025-1762

Event Tickets with Ticket Scanner <= 2.5.3 - Cross-Site Request Forgery to Arbitrary Ticket Deletion

2025-03-06 00:00
Krugov Artyom

Strategic Overview

Status
Patched in 2.5.4
Affected Version
<= 2.5.3
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2025-1762
View all Event Tickets with Ticket Scanner vulnerabilities

At a glance

CVE-2025-1762 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Event Tickets with Ticket Scanner WordPress plugin, affecting versions <= 2.5.3. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.5.4; sites on affected versions should update now. Disclosed March 2025, reported by Krugov Artyom.

Vulnerability Overview

The Event Tickets with Ticket Scanner plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.5.3. This is due to missing or incorrect nonce validation on the executeJSON() function. This makes it possible for unauthenticated attackers to delete arbitrary tickets via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

Event Tickets with Ticket Scanner <= 2.5.3 carries this weakness at executeJSON(), and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Event Tickets with Ticket Scanner the fix is 2.5.4: builds <= 2.5.3 are affected, anything from 2.5.4 onward is not.

Remediation

Update to version 2.5.4, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Event Tickets with Ticket Scanner: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Event Tickets with Ticket Scanner 2.5.4 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C