Loading vulnerability…
WordPress Core through version 6.2 is vulnerable to directory traversal via the wp_lang parameter. An unauthenticated attacker can manipulate this parameter to access and load arbitrary translation files from unintended locations. The provided content further indicates that if an attacker is able to place a crafted translation file on the target site, for example through an upload capability, the issue may be leveraged to trigger cross-site scripting by causing WordPress to load attacker-controlled translation content.
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.
No valid public exploits. Mallory filtered out 2 candidates as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
The content references CVE-2023-2745 in the context of fixing a false negative in a template, but does not provide technical details about the vulnerability itself.
The content references CVE-2023-2745 in the context of a fix removing an authentication requirement, but does not provide enough detail to determine the exact vulnerability type or impact.
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.