CVE-2022-47427

My Calendar <= 3.3.24.1 - Cross-Site Request Forgery

2023-01-03 00:00
rezaduty

Strategic Overview

Status
Patched in 3.3.25
Affected Plugin
My Calendar – Accessible Event Manager
Affected Version
<= 3.3.24.1
CVSS
7.1High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2022-47427
View all My Calendar – Accessible Event Manager vulnerabilities

At a glance

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

Vulnerability Overview

The My Calendar plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.3.24.1. This is due to missing or incorrect nonce validation on several functions handling the deletion of events and locations. This makes it possible for unauthenticated attackers to remove events or locations, 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 Calendar <= 3.3.24.1 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 Calendar the fix is 3.3.25: builds <= 3.3.24.1 are affected, anything from 3.3.25 onward is not.

Remediation

Update to version 3.3.25, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-47427https://www.wordfence.com/threat-intel/vulnerabilities/id/334570f7-967b-4792-934c-ebe4c4f18490https://nvd.nist.gov/vuln/detail/CVE-2022-47427

Related records

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