CVE-2026-1487
SQL Injection in LatePoint Plugin Allows Admin Data Manipulation
Publication date: 2026-03-03
Last updated on: 2026-03-03
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| latepoint | calendar_booking_plugin | to 5.2.7 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The LatePoint – Calendar Booking Plugin for Appointments and Events for WordPress has a vulnerability known as SQL Injection in all versions up to and including 5.2.7.
This vulnerability occurs because the plugin does not properly validate user-supplied JSON data during the JSON Import process.
As a result, authenticated users with Administrator-level access or higher can execute arbitrary SQL queries on the database.
How can this vulnerability impact me? :
An attacker exploiting this vulnerability can extract sensitive information from the database using time-based techniques.
They can also drop database tables or modify data, potentially causing data loss or corruption.
Because the attacker needs Administrator-level access, the impact is significant within environments where such access is granted.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know