CVE-2026-23805
SQL Injection in Media Search Enhanced ≤ 0.9.1 Allows Data Exposure
Publication date: 2026-02-19
Last updated on: 2026-02-24
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| patchstack | media_search_enhanced | to 0.9.1 (inc) |
| yoren_chang | media_search_enhanced | to 0.9.1 (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?
[{'type': 'paragraph', 'content': 'CVE-2026-23805 is a SQL Injection vulnerability found in the WordPress Media Search Enhanced Plugin versions up to and including 0.9.1.'}, {'type': 'paragraph', 'content': "This vulnerability allows a malicious actor to directly interact with the plugin's database by injecting malicious SQL commands, potentially leading to unauthorized data access or theft."}, {'type': 'paragraph', 'content': 'It is classified under the OWASP Top 10 category A3: Injection.'}] [1]
How can this vulnerability impact me? :
[{'type': 'paragraph', 'content': 'Exploitation of this vulnerability can allow an attacker with author or developer-level privileges to execute unauthorized SQL commands on the database.'}, {'type': 'paragraph', 'content': "This can lead to unauthorized access to sensitive data or theft of information stored within the plugin's database."}, {'type': 'paragraph', 'content': 'However, the vulnerability is considered low severity and low priority, and it is unlikely to be widely exploited.'}] [1]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': "This vulnerability is a SQL Injection issue in the WordPress Media Search Enhanced Plugin up to version 0.9.1. Detection typically involves identifying suspicious SQL queries or attempts to exploit the plugin's database interaction."}, {'type': 'paragraph', 'content': 'Since the vulnerability requires author or developer-level privileges to exploit, monitoring for unusual database queries or unauthorized access attempts related to the plugin can help detect exploitation attempts.'}, {'type': 'paragraph', 'content': 'Specific commands are not provided in the available resources, but common detection methods include:'}, {'type': 'list_item', 'content': 'Reviewing web server logs for suspicious input patterns that resemble SQL injection payloads targeting the plugin.'}, {'type': 'list_item', 'content': 'Using tools like sqlmap to test the plugin endpoints for SQL injection vulnerabilities.'}, {'type': 'list_item', 'content': 'Running database query logs to identify anomalous or unauthorized queries.'}] [1]
What immediate steps should I take to mitigate this vulnerability?
The primary and immediate mitigation step is to update the WordPress Media Search Enhanced Plugin to version 0.9.2 or later, where this SQL Injection vulnerability is resolved.
Additionally, enabling automatic updates for the plugin can help ensure rapid protection against this and future vulnerabilities.
Since exploitation requires author or developer-level privileges, reviewing and restricting user permissions to only trusted users can reduce the risk.