CVE-2026-15018: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in davejesch Database Collation Fix
The Database Collation Fix plugin for WordPress is vulnerable to time-based SQL Injection via the 'force-collation-algorithm' parameter in all versions up to, and including, 1.2.10 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. 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. Exploitation requires a trigger.txt file to be present in the plugin's directory (/wp-content/plugins/database-collation-fix/trigger.txt), a condition created by DesktopServer integration events such as site creation, copy, import, move, export, or deploy.
AI Analysis
Technical Summary
CVE-2026-15018 is a time-based SQL Injection vulnerability in the Database Collation Fix WordPress plugin, affecting all versions up to and including 1.2.10. The flaw is due to improper neutralization of special elements in the 'force-collation-algorithm' parameter, allowing unauthenticated attackers to append additional SQL queries. Successful exploitation depends on the presence of a trigger.txt file in the plugin directory, which is created by DesktopServer integration events. This vulnerability can be leveraged to extract sensitive information from the database without authentication.
Potential Impact
An unauthenticated attacker can exploit this vulnerability to perform time-based SQL Injection attacks, potentially extracting sensitive database information. The vulnerability does not allow modification or destruction of data (no integrity or availability impact), but confidentiality is impacted. Exploitation requires a specific file (trigger.txt) to be present, limiting the attack surface to environments using DesktopServer integration.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should verify the presence of the trigger.txt file and consider removing or restricting access to it. Additionally, avoid using the affected plugin versions in environments where DesktopServer integration creates this file. Monitor vendor channels for updates or patches addressing this vulnerability.
CVE-2026-15018: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in davejesch Database Collation Fix
Description
The Database Collation Fix plugin for WordPress is vulnerable to time-based SQL Injection via the 'force-collation-algorithm' parameter in all versions up to, and including, 1.2.10 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. 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. Exploitation requires a trigger.txt file to be present in the plugin's directory (/wp-content/plugins/database-collation-fix/trigger.txt), a condition created by DesktopServer integration events such as site creation, copy, import, move, export, or deploy.
CVSS v3.1
Score 5.3medium
Affected software
davejesch
Database Collation Fix
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-15018 is a time-based SQL Injection vulnerability in the Database Collation Fix WordPress plugin, affecting all versions up to and including 1.2.10. The flaw is due to improper neutralization of special elements in the 'force-collation-algorithm' parameter, allowing unauthenticated attackers to append additional SQL queries. Successful exploitation depends on the presence of a trigger.txt file in the plugin directory, which is created by DesktopServer integration events. This vulnerability can be leveraged to extract sensitive information from the database without authentication.
Potential Impact
An unauthenticated attacker can exploit this vulnerability to perform time-based SQL Injection attacks, potentially extracting sensitive database information. The vulnerability does not allow modification or destruction of data (no integrity or availability impact), but confidentiality is impacted. Exploitation requires a specific file (trigger.txt) to be present, limiting the attack surface to environments using DesktopServer integration.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should verify the presence of the trigger.txt file and consider removing or restricting access to it. Additionally, avoid using the affected plugin versions in environments where DesktopServer integration creates this file. Monitor vendor channels for updates or patches addressing this vulnerability.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-07-07T23:30:22.187Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a6daf59bf32cb7a346ced29
Added to database: 08/01/2026, 08:33:29 UTC
Last enriched: 08/08/2026, 14:25:31 UTC
Last updated: 09/16/2026, 22:01:32 UTC
Views: 30
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.