CVE-2026-1487
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 · uneditedThe LatePoint – Calendar Booking Plugin for Appointments and Events plugin for WordPress is vulnerable to SQL Injection via the JSON Import in all versions up to, and including, 5.2.7 due to insufficient validation on the user-supplied JSON data. This makes it possible for authenticated attackers, with Administrator-level access and above, to execute arbitrary SQL queries on the database that can be used to extract information via time-based techniques, drop tables, or modify data.
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 confidenceThe LatePoint WordPress booking plugin contains a SQL injection vulnerability in its JSON Import feature. Authenticated administrators can inject arbitrary SQL commands through insufficiently validated JSON data, allowing extraction of sensitive data, table modification, or deletion via time-based techniques.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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.
-
Confirm LatePoint plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for LatePoint booking plugin, or check the wp-content/plugins/ directory for the latepoint folderAffected if The plugin is present in the WordPress installation
-
Identify installed LatePoint versionIn WordPress admin_plugins list, click on the LatePoint plugin to view its version number, or check the main plugin file header in wp-content/plugins/latepoint/latepoint.php for the Version fieldAffected if The installed version is 5.2.7 or older (versions newer than 5.2.7 are patched)
-
Verify JSON Import feature existsNavigate through the LatePoint settings panel looking for an Import/JSON Import option typically under Settings or Tools menu within the LatePoint booking settingsAffected if The JSON Import feature is present and accessible in the admin interface
-
Check admin user access to JSON ImportReview user roles in WordPress admin under Users menu and check which roles have access to the LatePoint JSON Import functionalityAffected if Multiple administrator or editor accounts have access to the JSON Import feature (broader access increases exposure)
You are affected if LatePoint plugin is installed with version 5.2.7 or older and the JSON Import feature is enabled and accessible to your WordPress administrators.
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 dataUpdate the plugin to a version newer than 5.2.7. If immediate update is not possible, disable or restrict the JSON Import functionality to trusted administrators only.
- Consultation2.0 h
- Implementation2.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1487 — 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-2026-1487 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