LatepointWordPress extension
CVE-2024-43992
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 · uneditedImproper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Latepoint LatePoint allows Stored XSS.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 confidenceStored XSS vulnerability in LatePoint plugin allows authenticated attackers to inject malicious JavaScript code through unsanitized user input that gets stored and executed when other users view the affected page. The CVSS 5.4 indicates network attack vector, low attack complexity, low privileges required, and user interaction needed.
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
<= 4.9.91CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Locate LatePoint plugin versionAccess your WordPress admin panel, go to Plugins > Installed Plugins, find LatePoint, and note the version number displayed. Alternatively, check the main LatePoint plugin file (such as latepoint.php) for the 'Version' header comment.Affected if The installed version is 4.9.91 or lower.
-
Confirm LatePoint is activeVerify that the LatePoint plugin is currently activated in your WordPress site. Check the Plugins page in the admin panel.Affected if LatePoint is installed and active.
-
Identify LatePoint user input areasNavigate through LatePoint booking forms, customer registration fields, admin input panels, or any page where users can submit data through the plugin. Common areas include booking request forms, customer profile fields, and agent input forms.Affected if User input fields exist and accept data that gets stored in the database.
-
Inspect stored data for unsanitized contentIf you have database access, query LatePoint-related tables (typically wp_latepoint_* tables) for any unexpected script tags, HTML, or JavaScript code in user-submitted fields such as names, notes, or booking details.Affected if Database contains script tags or javascript: URLs in user-supplied fields that are not escaped.
-
Review page rendering for injected scriptsAs an administrator, view pages containing LatePoint booking widgets or admin dashboards. Use browser developer tools to inspect the page source and check for any executed script tags within LatePoint-rendered content.Affected if Rendered HTML in LatePoint pages contains unescaped user-supplied content including script tags.
Your environment is affected if LatePoint plugin version 4.9.91 or lower is installed and active, and unescaped user input data exists in LatePoint database tables or renders in the frontend.
Generated from the published advisory. Verify against your own configuration.
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 dataIdentify and sanitize/escape all user-supplied input fields in the LatePoint plugin before storing and displaying them. Apply context-appropriate output encoding when rendering data in web pages.
Fix this in Latepoint
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-43992 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-43992 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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