CVE-2026-16572

LogMyTrip <= 1.9 - Unauthenticated SQL Injection via 'tid' Cookie

Published Aug 3, 2026 CVSS 3.1 · 8.6 High EPSS < 1% KEV · Not listed
Description
The LogMyTrip WordPress plugin through 1.9 does not sanitize and escape a value taken from a cookie before using it in a SQL query, allowing unauthenticated users to perform SQL injection attacks on any page that renders one of the LogMyTrip WordPress plugin through 1.9's shortcodes.

Analysis

AI-generated

Technical impact

The LogMyTrip WordPress plugin, when at or below version 1.9, fails to sanitize a value obtained from the 'tid' cookie before embedding it in a SQL query. This oversight allows an unauthenticated user to inject arbitrary SQL statements into any page that renders one of the plugin’s shortcodes, potentially enabling data extraction, modification, or deletion.

Affected Systems

Any WordPress site that has installed LogMyTrip version 1.9 or earlier is exposed. The vulnerability specifically targets the plugin’s handling of the 'tid' cookie on pages that display the plugin's shortcodes. No additional software components or versions were identified beyond the plugin itself.

Risk and Exploitability

Because the flaw is exploitable without authentication, the potential impact is wide‑area database compromise, which could support data breach or case escalation. The CVSS score is 8.6, indicating high severity. The EPSS score is <1%, suggesting a low but non‑zero exploitation probability, and the vulnerability is not yet catalogued in CISA’s KEV list. An attacker can exploit the flaw by setting a crafted 'tid' cookie and causing the plugin to execute the injected SQL against the database.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the official plugin update to the latest version that removes the vulnerability.
  • If an update is not immediately possible, block or sanitize the 'tid' cookie at the web server or WAF level, ensuring the value is not passed directly to the database.
  • Alternatively, remove or disable the LogMyTrip plugin until a patched version is available.

Generated by OpenCVE AI on August 4, 2026 at 22:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Weaknesses CWE-20
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 8.6, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Ajohnwaters
Ajohnwaters logmytrip
Wordpress
Wordpress wordpress
Vendors & Products Ajohnwaters
Ajohnwaters logmytrip
Wordpress
Wordpress wordpress
Type Values Removed Values Added
Weaknesses CWE-20
CWE-89
Type Values Removed Values Added
Description The LogMyTrip WordPress plugin through 1.9 does not sanitize and escape a value taken from a cookie before using it in a SQL query, allowing unauthenticated users to perform SQL injection attacks on any page that renders one of the LogMyTrip WordPress plugin through 1.9's shortcodes.
Title LogMyTrip <= 1.9 - Unauthenticated SQL Injection via 'tid' Cookie
References
Weaknesses
  • CWE-89

    Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Sources

Status
PUBLISHED
Assigner
WPScan
Published
Updated
Aug 3, 2026, 4:08 PM
Reserved
Jul 22, 2026, 12:55 PM
Status
Deferred
Published
Aug 3, 2026, 7:16 AM
Modified
Aug 26, 2026, 4:31 PM