Is Database Collation Fix safe to use?

Laskyr does not give safety verdicts. No known unpatched vulnerabilities in the latest version (1.2.11). As of 2026-11-04. 2 issues are on record for older versions; version 1.2.8 or newer fixes all of them that state a fix. Keep Database Collation Fix on the latest version (1.2.11) and remove it if you do not use it.

Which versions of Database Collation Fix are vulnerable?

Known issues on record (newest first): SQL injection (1.2.10 and older); Cross-site request forgery (CSRF) (1.2.7 and older, fixed in 1.2.8). The full list with sources is on this page.

What is the latest version of Database Collation Fix?

1.2.11, according to wordpress.org (last updated 2026-07-10). It has 1,000+ active installs.

What should I do if my Database Collation Fix is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update database-collation-fix). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · database-collation-fix · data as of 2026-11-04

Is Database Collation Fix safe? Known vulnerabilities and latest version

Latest version: 1.2.11
Last updated: 2026-07-10
Active installs: 1,000+
Known issues on record: 2
Unpatched in latest: 0
Tested up to WP: 7.0.8 · PHP 5.3.1+

Convert tables using utf8mb4_unicode_520_ci or utf8_unicode_520_ci collation to a more portable Collation Algorithm. — by Dave Jesch

What to do

Update to the latest version (1.2.11). Anything older than 1.2.8 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
If you cannot update right away, deactivate it until you can.
Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get database-collation-fix --field=version shows what you run; wp plugin update database-collation-fix updates it.

Check your version

Known vulnerabilities

2 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

medium 5.3 CVE-2026-15018 · published 2026-08-01

SQL injection in Database Collation Fix (1.2.10 and older)

Affected: 1.2.10 and older
Fixed in: unknown
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

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.

NVD CVE-2026-15018 Wordfence advisory Code change (fix)Plugin source

high 8.8 CVE-2023-23997 · published 2023-07-11

Cross-site request forgery (CSRF) in Database Collation Fix (1.2.7 and older)

Affected: 1.2.7 and older
Fixed in: 1.2.8
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

Cross-Site Request Forgery (CSRF) vulnerability in Dave Jesch Database Collation Fix plugin <= 1.2.7 versions.

NVD CVE-2023-23997 Patchstack advisory

Recent activity

2026-07-10 — latest release on wordpress.org (1.2.11).
2026-08-01 — SQL injection disclosed (CVE-2026-15018), fix version not stated.
2023-07-11 — Cross-site request forgery (CSRF) disclosed (CVE-2023-23997), fixed in 1.2.8.

Free. We check the CVE feeds every day and email you only when a new issue for Database Collation Fix (database-collation-fix) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: SQL injection (1) · Cross-site request forgery (CSRF) (1)

Where this data comes from

Version, last update, installs: wordpress.org/plugins/database-collation-fix (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/database-collation-fix"><img src="https://laskyr.com/plugins/database-collation-fix/badge.svg" alt="Database Collation Fix vulnerability status"></a>

← Check another plugin · Free hacked-site scan