Loading vulnerability…
In Saleor, a headless GraphQL commerce platform, certain GraphQL mutations failed to properly validate the type of ID input, allowing authenticated users to access database objects they should not have access to. Specifically, this flaw could be exploited to estimate row counts in tables with sequential primary keys and to expose sensitive information such as staff and customer email addresses and full names via the assignNavigation() mutation.
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 is a proof-of-concept (POC) for CVE-2022-39275, a vulnerability in Saleor, an open-source e-commerce platform. The repository is a fork of Saleor's official platform at a specific commit and includes all necessary submodules and configuration to set up a local instance using Docker Compose. The README provides detailed setup instructions, including how to initialize the database and create admin users. The exploit itself is not a script but a process: after setting up the vulnerable Saleor instance, the user is instructed to use the GraphQLer tool to discover and craft requests that trigger the vulnerability. The repository includes configuration files, environment files, and code for the Saleor backend, dashboard, and React-based storefront, as well as payment integration code for Mollie and Adyen. The main attack vector is network-based, targeting the Saleor GraphQL API. Several local endpoints are exposed for the API, storefront, dashboard, and supporting services. The repository is structured as a monorepo with multiple submodules and a focus on developer setup for vulnerability testing, not for production use.
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.