CVE-2023-32523 is an improper authentication vulnerability in Trend Micro Mobile Security (Enterprise) 9.8 SP5, including builds up to Critical Patch 3. The flaw affects widget functionality exposed by the application and allows an attacker to bypass authentication by abusing session handling and user initialization logic. Specifically, the vulnerable workflow trusts a user-controlled session value to populate the username stored in server-side session state, and the associated user-handling logic can automatically create a non-existent account with a blank password. As a result, an unauthenticated attacker can obtain a valid authenticated application session without legitimate credentials. The vulnerability is especially dangerous because it can be chained with separate unrestricted file upload and local file inclusion flaws in the same product to achieve pre-authenticated remote code execution.
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 public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.