CVE-2026-16572 LogMyTrip CVE debrief

Who should care

Users of LogMyTrip WordPress plugin through 1.9, security teams, and WordPress administrators should be aware of this vulnerability. They should verify affected scope, check for vendor remediation or patches, and implement compensating controls and monitoring as needed. This vulnerability could allow unauthenticated users to perform SQL injection attacks, potentially leading to data breaches or other security incidents. Affected operators and platforms should review their deployments and take necessary actions.

Technical summary

The LogMyTrip WordPress plugin through 1.9 is vulnerable to SQL injection attacks. This is due to the plugin not sanitizing and escaping a value taken from a cookie before using it in a SQL query. Unauthenticated users can exploit this vulnerability on any page that renders one of the LogMyTrip WordPress plugin through 1.9's shortcodes. Users should verify affected scope and check for vendor remediation or patches. The vulnerability could allow data breaches or other security incidents.

Defensive priority

Low priority, limited evidence, verify affected scope

Recommended defensive actions

• Verify affected scope and inventory
• Check for vendor remediation or patches
• Implement compensating controls and monitoring
• Review relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed

Evidence notes

The evidence for this CVE is limited. 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. This could allow unauthenticated users to perform SQL injection attacks. Verify the affected scope and check for vendor remediation or patches. The CVE record was published on 2026-08-03T07:16:42.227Z and has not been modified since then. Evidence is based on CVE and NVD details.

Official resources