Skip to main content

WPML Multilingual CMS EUVDEUVD-2026-72698

| CVE-2026-17509 MEDIUM
SQL Injection (CWE-89)
2026-09-08 Wordfence GHSA-6xgg-64gv-xp85
6.5
CVSS 3.1 · Vendor: Wordfence
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Register/obtain Subscriber-level WordPress account
  2. Delivery
    Access WPML translation endpoint (auth bypass)
  3. Exploit
    Inject time-based SQL payload in elementIds
  4. Execution
    Infer database contents via response timing
  5. Impact
    Extract credentials and sensitive data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Persistence

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires a valid WordPress account of any role, including Subscriber (the lowest default role). The authorization bypass is the key enabling condition: the plugin's capability check callback fails to execute, so no elevated role is needed beyond basic authentication. WordPress user registration must be enabled on the target site (the default is configurable by the admin). Sites with user registration disabled have a significantly reduced attack surface, as an attacker would need to obtain credentials through another means. The injection targets a specific parameter ('elementIds') within WPML's translation management functionality, so the WPML plugin must be installed and active. No specific non-default WPML configuration is required beyond installation of a vulnerable version (≤4.9.5).

Impact

The provided CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, score 6.5) accurately captures the risk profile: network-reachable, low complexity, but gated behind any form of authentication (Subscriber). The authorization bypass is the critical enabler - without it, the SQL injection would require a higher-privileged role with access to translation management. With it, any registered WordPress user (e.g., newsletter subscribers, commenters with accounts) can trigger the injection. The time-based nature slows exploitation but does not prevent it; automated tooling such as sqlmap can extract full database contents given sufficient time. Confidentiality impact is high (full DB read), while integrity and availability are not directly affected by this injection type. No EPSS data was provided, and CISA KEV status is not confirmed. Given WPML's large install base (millions of sites), the low authentication bar, and the completeness of the authorization bypass, this should be treated as a high-priority remediation item for any site with user registration enabled.

Exploit ScenarioDerived

An attacker registers a free account on a target WordPress site (Subscriber role) and sends crafted POST requests to the WPML translation management endpoint with a time-delay SQL payload injected into the 'elementIds' parameter. Because the authorization callback fails silently, the request is processed without privilege checks. The attacker uses time-based inference (e.g., SLEEP() conditionals) to systematically enumerate and extract database contents - including WordPress user credentials, email addresses, and any sensitive plugin data - without direct query output.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 08, 2026

Time-based blind SQL injection in the WPML Multilingual CMS WordPress plugin (all versions through 4.9.5) enables authenticated attackers with Subscriber-level access to exfiltrate sensitive database contents via the 'elementIds' parameter. The vulnerability is compounded by an authorization bypass: the plugin's registered authorization callback silently fails to execute, inadvertently granting any authenticated user - regardless of role - access to administrative translation endpoints that are intended to be admin-only. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, but the low privilege bar (Subscriber) and widespread deployment of WPML make this a meaningful data-exposure risk on affected sites.

RemediationAI

Update WPML Multilingual CMS to a version above 4.9.5 as soon as a patched release is confirmed via the vendor changelog at https://wpml.org/category/changelog/. The Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/8e7e7d78-de2f-4bdf-b04a-373463bd4d9c should be monitored for the confirmed fixed version. No exact fix version was independently confirmed from the available input data. As a compensating control while a patch is pending, site administrators should consider disabling open user registration (Settings > General > Membership) to eliminate the Subscriber-level access vector, though this may impact legitimate site functionality. Wordfence firewall rules (if the premium tier is active) may provide virtual patching against the specific injection pattern. Restricting access to the affected translation endpoints via a WAF rule targeting the 'elementIds' parameter in relevant REST or admin-ajax requests is an additional short-term option.

Affected VersionsENISA

WPML Multilingual CMS 0 ≤4.9.5

Affected Packages

euvd wpml_multilingual_cms no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

WPML Multilingual CMS (CPE: cpe:2.3:a:wpml:wpml_multilingual_cms:*:*:*:*:*:*:*:*) is a premium WordPress plugin widely used to build multilingual websites. The flaw (CWE-89 - Improper Neutralization of Special Elements used in an SQL Command) arises in the plugin's translation management functionality where the 'elementIds' parameter is appended to an existing SQL query without adequate escaping or use of prepared statements. The injection is time-based (blind), meaning the attacker infers data by observing response delays rather than direct output. An intertwined authorization defect - a registered WordPress capability check whose callback never fires - elevates the exploitable surface to all authenticated users, not just those with the translation-management capability the code intended to require.

Know when Wpml gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Wordfence) PRIMARY 6.5 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
vuln.today AI 6.5 MEDIUM

Network-reachable with no complexity; PR:L reflects required Subscriber auth; C:H for full DB read; I:N and A:N as injection is read-only and blind.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (Wordfence).

CVSS VectorVendor: Wordfence

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

DescriptionCVE.org

The WPML Multilingual CMS plugin for WordPress is vulnerable to time-based SQL Injection via the ‘elementIds’ 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 Subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. This vulnerability is exploitable due to an authorization bypass where the registered authorization callback fails to execute, allowing any authenticated user regardless of role to access administrative translation functionalities.

Threat Intelligence Overview

EPSS Score
0.2%
Top 85% exploitable
Prevalence
High
WPML has millions of active installs across WordPress sites worldwide
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
High
Technical Impact
Partial

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

More in Wpml

View all
CVE-2024-6386 CRITICAL POC
9.9 Aug 21

Remote code execution in the WPML WordPress multilingual plugin (versions up to and including 4.6.12) allows Contributor

CVE-2015-2314 HIGH POC
7.5 Mar 17

SQL injection vulnerability in the WPML plugin before 3.1.9 for WordPress allows remote attackers to execute arbitrary S

CVE-2015-2791 MEDIUM POC
6.4 Mar 30

The "menu sync" function in the WPML plugin before 3.1.9 for WordPress allows remote attackers to delete arbitrary posts

CVE-2015-2792 HIGH POC
7.5 Mar 30

The WPML plugin before 3.1.9 for WordPress does not properly handle multiple actions in a request, which allows remote a

CVE-2018-18069 MEDIUM POC
6.1 Oct 08

process_forms in the WPML (aka sitepress-multilingual-cms) plugin through 3.6.3 for WordPress has XSS via any locale_fil

CVE-2015-2315 MEDIUM POC
4.3 Mar 17

Cross-site scripting (XSS) vulnerability in the WPML plugin before 3.1.9 for WordPress allows remote attackers to inject

CVE-2022-45071 HIGH
8.8 Nov 17

Cross-Site Request Forgery (CSRF) vulnerability in WPML Multilingual CMS premium plugin <= 4.5.13 on WordPress. Rated hi

CVE-2025-3488 MEDIUM
6.4 May 02

The WPML plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's wpml_language_switcher short

CVE-2022-38974 MEDIUM
4.3 Nov 18

Broken Access Control vulnerability in WPML Multilingual CMS premium plugin <= 4.5.10 on WordPress allows users with sub

CVE-2022-45072 MEDIUM
4.3 Nov 17

Cross-Site Request Forgery (CSRF) vulnerability in WPML Multilingual CMS premium plugin <= 4.5.13 on WordPress. Rated me

CVE-2022-38461 MEDIUM
4.3 Nov 17

Broken Access Control vulnerability in WPML Multilingual CMS premium plugin <= 4.5.10 on WordPress allows users with a s

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy