dbcve.org
LatepointWordPress extension

CVE-2024-43945

HIGH · 8.8 CVSS v3.1 Published 2024-10-21
Fix available
A fix is available. Upgrade to after 4.9.91 or later.
See remediation →
95/100
Remediation priority · Urgent
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
Cross-Site Request Forgery (CSRF) vulnerability in Latepoint LatePoint allows Cross Site Request Forgery.This issue affects LatePoint: from n/a through 4.9.91.

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 · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the LatePoint WordPress booking plugin allows attackers to trick authenticated users into unknowingly submitting malicious requests to the plugin's endpoints. The lack of proper anti-CSRF token validation on sensitive actions enables attackers to perform unauthorized operations on behalf of victims who have active sessions.

MitigationUpdate LatePoint to the latest patched version, or if no update is available, implement WordPress nonce verification on all form submissions and AJAX actions within the plugin.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
LatepointWordPress extension
Affected:<= 4.9.91

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Check LatePoint plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins > locate LatePoint and view the version number displayed under the plugin name
    Affected if Version displayed is 4.9.91 or lower
  2. Verify version via file inspection
    Access the plugin files via FTP or file manager, open the main plugin file (typically latepoint.php or similar in wp-content/plugins/latepoint) and locate the 'Version' header comment
    Affected if Version header shows 4.9.91 or lower
  3. Confirm WordPress version context
    While not directly related to CVE-2024-43945, ensure your WordPress core is up to date as this affects the overall security posture
    Affected if Not directly applicable to this CVE check

If the installed LatePoint version is 4.9.91 or lower, the plugin is affected by this CSRF vulnerability due to missing anti-CSRF token validation on sensitive actions.

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.

From vendor data
Upgrade available Upgrade to a release after 4.9.91
Interim mitigation

Update LatePoint to the latest patched version, or if no update is available, implement WordPress nonce verification on all form submissions and AJAX actions within the plugin.

Fix this in Latepoint Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-43945 — 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-2024-43945 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