CVE-2026-15018
Received Received - Intake

Time-Based SQL Injection in Database Collation Fix WordPress Plugin

Publication date: 2026-08-01

Last updated on: 2026-08-01

Assigner: Wordfence

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 Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-01
Last Modified
2026-08-01
Generated
2026-08-01
AI Q&A
2026-08-01
EPSS Evaluated
N/A
NVD
CVE-2026-15018
EUVD
EUVD-2026-51754

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
wordfence database_collation_fix to 1.2.10 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
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 Quick Actions

Instant insights powered by AI
Executive Summary

The Database Collation Fix plugin for WordPress has a time-based SQL Injection vulnerability in versions up to 1.2.10. The flaw exists due to insufficient escaping of the 'force-collation-algorithm' parameter and lack of proper SQL query preparation. Unauthenticated attackers can inject additional SQL queries to extract sensitive database information.

Detection Guidance

Check for the presence of the trigger.txt file in the plugin's directory (/wp-content/plugins/database-collation-fix/trigger.txt). This file indicates potential exploitation attempts or conditions created by DesktopServer integration events.

Impact Analysis

Attackers could steal sensitive data from your WordPress database, such as user credentials or personal information. Exploitation requires a specific file (trigger.txt) in the plugin's directory, which may be present due to certain DesktopServer operations like site creation or migration.

Compliance Impact

This vulnerability could lead to unauthorized access and exfiltration of personal data, violating GDPR and HIPAA requirements for data protection and security. Organizations using this plugin may face compliance violations and potential fines if exploited.

Mitigation Strategies

Update the Database Collation Fix plugin to the latest version beyond 1.2.10. Remove any existing trigger.txt file from the plugin's directory. Review database logs for suspicious SQL queries or unauthorized access attempts.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-15018. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart