Loading vulnerability…
Appsmith (<= 1.94) contains an access-control flaw in the action execution API for publicly accessible (published) applications. By sending viewMode=false (or omitting the viewMode parameter) to POST /api/v1/actions/execute, an unauthenticated user can cause the server to execute unpublished “edit-mode” actions rather than being restricted to published actions only. This breaks the intended publish boundary between what public viewers can run and what is only available in edit mode, enabling unauthorized execution of edit-mode queries/APIs and associated side effects.
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.
POST /api/v1/actions/execute and reduce the risk of edit-mode action execution.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.
6 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.