CVE-2026-16572: LogMyTrip (WordPress plugin) · SQL Injection
Affects LogMyTrip (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 8.6 High.
Data as of 1 Nov 2026, 22:58 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 3 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LogMyTrip | Affected
| Fixed in– |
AI-suggested
Until an official fix is released, users should consider disabling the LogMyTrip plugin or removing shortcodes that render its content to prevent exploitation.
Description
The LogMyTrip WordPress plugin up to version 1.9 contains a SQL injection vulnerability due to improper sanitization and escaping of a cookie value used in SQL queries. This flaw allows unauthenticated attackers to inject SQL code via any page rendering the plugin's shortcodes. The vulnerability has a high severity score of 8.6 and impacts confidentiality but not integrity or availability.