The Translate Multilingual sites WordPress plugin before version 2.3.3 contains an authenticated SQL injection vulnerability. The vulnerability exists in the functionality for adding a new language via the settings page, where user-supplied input is not properly sanitized. By crafting a language name with specific special characters, an attacker can bypass the intended use of backticks in the SQL query and inject arbitrary SQL code. This allows for time-based blind SQL injection attacks.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository is a comprehensive, interactive report and proof-of-concept (PoC) for CVE-2022-3141, a critical SQL injection vulnerability in the TranslatePress WordPress plugin (versions prior to 2.3.3). The repository is structured as a Next.js/React web application, with TypeScript code providing the vulnerability analysis, exploit steps, and mitigation details. The main exploit capability is an authenticated SQL injection via improper sanitization of the 'language code' parameter, allowing an attacker to inject SQL through the 'trp_settings[translation-languages][]' POST parameter to '/wp-admin/options.php'. The PoC demonstrates both manual exploitation (using a crafted payload such as '` OR SLEEP(5)#') and automated exploitation with sqlmap. The repository does not contain a weaponized exploit, but provides clear, actionable steps and code snippets for reproducing the attack in a controlled environment. No hardcoded IPs or domains are present, but the HTTP endpoint and vulnerable parameter are clearly identified. The codebase is primarily TypeScript/React, with supporting configuration and static files.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.