CVE-2022-47440

My Tickets <= 1.9.10 - Cross-Site Request Forgery

2023-01-04 00:00
rezaduty

Strategic Overview

Status
Patched in 1.9.11
Affected Version
<= 1.9.10
CVSS
6.5Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2022-47440
View all My Tickets – Accessible Event Ticketing vulnerabilities

At a glance

CVE-2022-47440 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the My Tickets WordPress plugin, affecting versions <= 1.9.10. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires no authentication. The issue is fixed in version 1.9.11; sites on affected versions should update now. Disclosed January 2023, reported by rezaduty.

Vulnerability Overview

The My Tickets plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.9.10. This is due to missing or incorrect nonce validation on several of its functions including mt_reports_page and mt_import_settings. This makes it possible for unauthenticated attackers to send mass-emails to users and import new plugin settings, via 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. A successful exploit has high impact on integrity.

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

Reaching this weakness in My Tickets <= 1.9.10 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 My Tickets the fix is 1.9.11: builds <= 1.9.10 are affected, anything from 1.9.11 onward is not.

Remediation

Update to version 1.9.11, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to My Tickets: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: My Tickets 1.9.11 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