CVE-2026-4060
Time-Based SQL Injection in Geo Mashup WordPress Plugin
Publication date: 2026-05-02
Last updated on: 2026-05-05
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| geo_mashup | geo_mashup | to 1.13.18 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The Geo Mashup plugin for WordPress has a Time-Based SQL Injection vulnerability in the 'sort' parameter in all versions up to and including 1.13.18.
This vulnerability exists because the plugin does not properly escape or prepare the user-supplied 'sort' parameter in SQL queries. Although the esc_sql() function is used, it is ineffective in the ORDER BY clause since the value is not enclosed in quotes.
While a sanitizer was added in version 1.13.18, it only applies to AJAX code paths and not to other code paths like render-map.php or template tags, allowing unauthenticated attackers to inject additional SQL queries.
Attackers can exploit this to perform time-based blind SQL injection attacks to extract sensitive information from the database.
How can this vulnerability impact me? :
This vulnerability allows unauthenticated attackers to perform SQL injection attacks that can extract sensitive information from the database.
Because the attack is time-based blind SQL injection, attackers can infer data by measuring response times, potentially exposing confidential data without direct error messages.
The CVSS score of 7.5 indicates a high severity, meaning the impact on confidentiality is high, though integrity and availability are not affected.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthenticated attackers to extract sensitive information from the database via a time-based blind SQL injection. This exposure of sensitive data could lead to non-compliance with data protection regulations such as GDPR and HIPAA, which require the protection of personal and sensitive information from unauthorized access.
Specifically, the ability to extract sensitive information without authentication increases the risk of data breaches, which are subject to mandatory reporting and can result in penalties under these regulations.