CVE-2026-4060
HighSummary
The Geo Mashup plugin for WordPress is vulnerable to Time-Based SQL Injection via the 'sort' parameter in all versions up to and including 1.13.18. This is due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query.
Risk Assessment
Unauthenticated attackers can append additional SQL queries into existing queries, potentially leading to the extraction of sensitive information from the database. This poses a serious threat to the organization's data security.
Recommendation
It is recommended to update the Geo Mashup plugin to the latest version to mitigate the vulnerability. Additionally, conducting a database security audit and implementing further SQL Injection protection mechanisms is advisable.
Other vulnerabilities in Geo Mashup plugin for WordPress
See all- CVE-2026-4062High
The Geo Mashup plugin for WordPress is vulnerable to Time-Based SQL Injection via the 'object_ids' and 'exclude_object_ids' parameters in all versions up to and including 1.13.18. This is due to insufficient escaping on the user supplied parameters and lack of sufficient preparation on the existing SQL query.
- CVE-2026-4061High
The Geo Mashup plugin for WordPress is vulnerable to Time-Based SQL Injection via the 'map_post_type' parameter in all versions up to and including 1.13.18. The issue arises from improper input handling, allowing unauthenticated attackers to inject additional SQL queries.
Original NVD description (English source)
The Geo Mashup plugin for WordPress is vulnerable to Time-Based SQL Injection via the 'sort' parameter in all versions up to, and including, 1.13.18. This is due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. The `esc_sql()` function is applied but is ineffective in the `ORDER BY` context because the value is not enclosed in quotes. Additionally, while a `sanitize_sort_arg()` allowlist-based sanitizer was added in version 1.13.18, it is only applied in the AJAX code path (`sanitize_query_args()`) and not in the `render-map.php` or template tag code paths. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database via a time-based blind approach.