LiveActive security incident?Get immediate response
CVE Record

CVE-2023-24388: WordPress Booking calendar, Appointment Booking System Plugin <= 3.2.3 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in WpDevArt Booking calendar, Appointment Booking System plugin <= 3.2.3 versions affects plugin forms actions (create, duplicate, edit, delete).

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a CSRF flaw in the WpDevArt Booking calendar, Appointment Booking System WordPress plugin. If an administrator is tricked into interacting with malicious content while logged in, plugin form actions such as create, duplicate, edit, or delete could be performed without proper authorization intent.

Executive priority

Treat this as a moderate-priority WordPress hygiene issue. It is not documented as actively exploited, but it can alter booking-related data if an authenticated user is tricked. Prioritize internet-facing business sites that rely on booking functionality.

Technical view

CVE-2023-24388 affects the booking-calendar WordPress plugin through version 3.2.3. The issue is CWE-352 CSRF in plugin form actions. CVSS 3.1 is 5.4, network reachable, low attack complexity, user interaction required, no privileges required, with low integrity impact only.

Likely exposure

Exposure is limited to WordPress sites that have the WpDevArt Booking calendar, Appointment Booking System plugin installed at version 3.2.3 or earlier. The source bundle does not provide install counts, affected configurations beyond plugin forms, or a named fixed version.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. Practical exploitation would require user interaction and likely depends on a logged-in site user with access to the vulnerable plugin forms being induced to trigger an unwanted state-changing action.

Researcher notes

Evidence is concise: the public record names CSRF in plugin form actions and version scope through 3.2.3. No source in the bundle provides exploit details, proof-of-concept status, fixed version, or mitigation specifics, so remediation should be verified against vendor or Patchstack guidance.

Mitigation direction

  • Inventory WordPress sites for the booking-calendar plugin.
  • Check Patchstack and vendor guidance for a fixed release or mitigation.
  • Update the plugin if a supported patched version is available.
  • Disable or remove the plugin if no safe supported version is available.
  • Limit administrative access to trusted users only.

Validation and detection

  • Confirm whether the booking-calendar plugin is installed on each WordPress site.
  • Flag installed versions 3.2.3 or earlier for remediation review.
  • Review recent plugin activity for unexpected create, duplicate, edit, or delete actions.
  • Verify vendor or Patchstack guidance before closing remediation.
  • Confirm no public route or workflow depends on an unsafe plugin version.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-24388 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2023-24388Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
WpDevArtBooking calendar, Appointment Booking Systembooking-calendar, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.