dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2026-2324

MEDIUM · 6.1 CVSS v3.1 Published 2026-03-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The LatePoint – Calendar Booking Plugin for Appointments and Events plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 5.2.7. This is due to missing or incorrect nonce validation on the reload_preview() function. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The LatePoint WordPress plugin versions up to 5.2.7 contain a CSRF vulnerability in the reload_preview() function due to missing or incorrect nonce validation. This allows unauthenticated attackers to forge administrative requests that can modify plugin settings and inject malicious web scripts by tricking site administrators into clicking crafted links.

MitigationUpdate to version 5.2.8 or later which implements proper nonce validation. Until then, warn administrators not to click untrusted links and consider temporarily disabling the plugin if high-risk.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if LatePoint plugin is installed
    Locate the LatePoint plugin directory in the WordPress wp-content/plugins folder and open the main plugin file to find the version number in the plugin header
    Affected if The plugin is not found or cannot be located in the WordPress installation
  2. Compare installed version to affected range
    Read the version string from the plugin header (typically labeled 'Version') and compare it numerically to 5.2.7; versions 5.2.7 and lower are affected
    Affected if The installed version is 5.2.7 or any earlier version (e.g., 5.2.6, 5.2.5, etc.)
  3. Verify the reload_preview function exists and is accessible
    Examine the plugin source code for the reload_preview() function and confirm it handles preview-related operations without proper nonce validation checks
    Affected if The function exists and lacks proper nonce verification (missing wp_verify_nonce or check_admin_referer calls)
  4. Check if the vulnerable endpoint is exposed
    Test whether the reload_preview action is registered in WordPress wp_ajax hooks (for logged-in admins) or wp_ajax_nopriv hooks (for unauthenticated users)
    Affected if The action is registered and reachable without authentication (wp_ajax_nopriv)

A user is affected if the LatePoint plugin is installed with version 5.2.7 or lower and the reload_preview function is accessible without proper nonce validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to version 5.2.8 or later which implements proper nonce validation. Until then, warn administrators not to click untrusted links and consider temporarily disabling the plugin if high-risk.

Recommended fix Moderate confidence

Version 5.2.8 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the LatePoint – Calendar Booking Plugin for Appointments and Events
  4. 4. Check the current version number to confirm it is 5.2.7 or below
  5. 5. If an update is available, click 'Update Now' to update to version 5.2.8 or later
  6. 6. Alternatively, download the latest version from the WordPress plugin repository and upload it manually
  7. 7. After updating, verify the reload_preview() function now includes proper nonce validation

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2324 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2324 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data