WP Travel <= 10.1.3 - Authenticated (Author+) SQL Injection
Strategic Overview
- Status
- Patched in 10.1.4
- Affected Version
<= 10.1.3- CVSS
- 6.5Medium
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE-2025-22691
At a glance
CVE-2025-22691 is a medium-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the WP Travel WordPress plugin, affecting versions <= 10.1.3. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Author level or above. The issue is fixed in version 10.1.4; sites on affected versions should update now. Disclosed January 2025, reported by Trương Hữu Phúc (truonghuuphuc).
Vulnerability Overview
The WP Travel plugin for WordPress is vulnerable to SQL Injection in versions up to, and including, 10.1.3 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with author-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality.
CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Reaching this weakness in WP Travel <= 10.1.3 takes an account at Author level or above. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.
A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For WP Travel the fix is 10.1.4: builds <= 10.1.3 are affected, anything from 10.1.4 onward is not.
Remediation
Update to version 10.1.4, or a newer patched version
How does WordSec protect against this?
An attacker needs Author access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Travel 10.1.4 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in WP Travel – Ultimate Travel Booking System, Tour Management Engine
- 7.5CVE-2023-47224: WP Travel <= 7.7.0 Missing Authorization
CVE-2023-47224 - 6.5CVE-2024-53813: WP Travel <= 9.6.0 Missing Authorization
CVE-2024-53813 - 5.3CVE-2026-18042: Travel <= 12.0.1 Missing Authorization
CVE-2026-18042 - 5.3CVE-2026-13144: Travel <= 12.0.1 Missing Authorization
CVE-2026-13144 - 5.3CVE-2026-13146: Travel <= 12.0.1 Insecure Direct Object Reference
CVE-2026-13146 - 5.3CVE-2026-13143: WP Travel Payment Bypass
CVE-2026-13143 - 5.3CVE-2026-11868: Travel <= 11.7.0 Missing Authorization
CVE-2026-11868 - 5.3CVE-2026-24568: Travel <= 11.1.0 Missing Authorization
CVE-2026-24568
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C