CVE-2026-6457
Time-Based Blind 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.19 (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 known as time-based blind SQL Injection. This occurs via the 'geo_mashup_null_fields' parameter in all versions up to and including 1.13.19. The issue arises because the plugin does not properly escape user-supplied input and does not sufficiently prepare the existing SQL query. As a result, authenticated users with subscriber-level access or higher can append additional SQL queries to the existing ones.
This allows attackers to extract sensitive information from the database by exploiting the SQL injection flaw.
How can this vulnerability impact me? :
This vulnerability can allow an authenticated attacker with subscriber-level access or above to extract sensitive information from the database by injecting additional SQL queries. This can lead to unauthorized disclosure of sensitive data stored within the WordPress site's database.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows authenticated attackers with subscriber-level access to perform time-based blind SQL Injection, potentially extracting sensitive information from the database.
This exposure of sensitive data could lead to non-compliance with data protection regulations such as GDPR and HIPAA, which require safeguarding personal and sensitive information against unauthorized access.