CVE-2026-12248 WPML CVE debrief

Who should care

WordPress users with the WPML Multilingual CMS plugin installed, particularly those with translator-level access and above, should be aware of this vulnerability and take necessary precautions to prevent exploitation. This includes restricting translator-level access and above, monitoring for suspicious database queries, and applying vendor patches when available. Additionally, users should review compensating controls for exposed systems while remediation is scheduled and verified.

Technical summary

The WPML Multilingual CMS plugin for WordPress is vulnerable to SQL Injection via the 'sorting' parameter in all versions up to, and including, 4.9.5 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with translator-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

Defensive priority

Authenticated attackers with translator-level access and above could exploit this vulnerability to extract sensitive information from the database.

Recommended defensive actions

• Inventory and verify installed plugin versions
• Restrict translator-level access and above
• Monitor for suspicious database queries
• Apply vendor patches when available
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and NVD entry provide details about the vulnerability, but further information about the affected scope and vendor remediation is limited. The WPML Multilingual CMS plugin for WordPress versions up to and including 4.9.5 are vulnerable to SQL Injection. Authenticated attackers with translator-level access and above could exploit this vulnerability to extract sensitive information from the database. However, specific details about the number of affected installations, potential data exposure, and exact remediation steps are not provided in the available sources.

Official resources