Loading vulnerability…
Comments Like Dislike for WordPress through version 1.2.0 contains a missing capability check in the restore_settings function when it is invoked through an AJAX action. Authenticated users with minimal privileges, including subscribers, can invoke the action to reset the plugin's settings. Version 1.2.0 only partially addressed the issue because the nonce remains available to subscriber-level users.
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.
This repository contains a proof-of-concept (PoC) exploit for CVE-2023-3244, a vulnerability in the 'comments-like-dislike' WordPress plugin (versions <= 1.2.0). The vulnerability allows any authenticated user, including those with minimal privileges (such as subscribers), to reset the plugin's settings to default via an unprotected AJAX action (cld_settings_restore_action). The main exploit script, 'POC-CVE-2023-3244.py', is a Python script that logs into a target WordPress site using provided low-privilege credentials and then issues a GET request to the vulnerable AJAX endpoint to trigger the settings reset. The repository also includes a README with usage instructions and references, and a license file. No weaponized or post-exploitation payloads are present; the exploit is a functional PoC demonstrating the access control flaw.
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.