CVE-2025-46241

Appointment Booking Calendar <= 1.3.92 - Cross-Site Request Forgery to SQL Injection

2025-04-22 00:00
astra.r3verii

Strategic Overview

Status
Patched in 1.3.93
Affected Version
<= 1.3.92
CVSS
6.5Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2025-46241
View all Appointment Booking Calendar vulnerabilities

At a glance

CVE-2025-46241 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Appointment Booking Calendar WordPress plugin, affecting versions <= 1.3.92. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 1.3.93; sites on affected versions should update now. Disclosed April 2025, reported by astra.r3verii.

Vulnerability Overview

The Appointment Booking Calendar plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.3.92. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to inject SQL queries 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. A successful exploit has high impact on confidentiality.

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

Reaching this weakness in Appointment Booking Calendar <= 1.3.92 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 Appointment Booking Calendar the fix is 1.3.93: builds <= 1.3.92 are affected, anything from 1.3.93 onward is not.

Remediation

Update to version 1.3.93, or a newer patched version

How does WordSec protect against this?

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