CVE-2026-4061
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 vulnerability called Time-Based SQL Injection in the 'map_post_type' parameter in all versions up to and including 1.13.18.
This happens because the plugin removes WordPress's built-in magic quotes protection by calling stripslashes_deep($_POST), and then it uses the unsanitized 'map_post_type' value directly in an SQL IN clause without proper escaping or preparation.
While one branch of the code correctly escapes SQL inputs, the vulnerable branch does not, allowing attackers to inject additional SQL queries.
An unauthenticated attacker can exploit this to extract sensitive information from the database using a time-based blind SQL injection technique, but only if the Geo Search feature is enabled in the plugin settings.
How can this vulnerability impact me? :
This vulnerability allows unauthenticated attackers to perform time-based blind SQL injection attacks on your WordPress site using the Geo Mashup plugin.
Attackers can extract sensitive information from your database without needing any privileges or user interaction.
The impact includes potential data breaches and exposure of confidential data, which can compromise the security and privacy of your website and its users.
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, since the vulnerability enables extraction of sensitive information without authentication, it increases the risk of data breaches that violate confidentiality requirements mandated by these standards.