# ApostropheCMS import-export: NoSQL injection via update-key value lets a crafted import match and overwrite an unidentified document Advisory record · `GHSA-jqw5-w6h3-44g6` - **Identifiers:** `GHSA-jqw5-w6h3-44g6` · `CVE-2026-113662` - **State:** Confirmed - **Severity:** CVSS 5.4 Medium - **Critical:** No - **Weakness (CWE):** [CWE-284](https://cwe.mitre.org/data/definitions/284.html) · [CWE-943](https://cwe.mitre.org/data/definitions/943.html) - **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md) · [Other injection](https://agentprime.io/advisories/tag/injection.md) - **Published:** 20 Oct 2026 - **Updated:** 20 Oct 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 20 Oct 2026, 18:19 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `@apostrophecms/import-export` (npm): affected `<3.7.0`; fixed in `3.7.0` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > The @apostrophecms/import-export npm package, versions before 3.7.0, is affected. An archive can include an update-key property whose value is a MongoDB query operator, such as { $ne: null }, and the import uses that value to match and overwrite an existing document. An attacker needs an authenticated session with import access to the target type, such as the built-in contributor role, and no admin interaction. The source reports that a matched document can be overwritten even when the importer did not specify its identifying field. Upgrade to version 3.7.0 or later. Written 31 Oct 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 5.4 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.0030, the 22nd percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 13:33 UTC: First seen by agentprime - 31 Oct 2026, 13:33 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-jqw5-w6h3-44g6) ## Sources - [GitHub Advisory Database: GHSA-jqw5-w6h3-44g6](https://github.com/advisories/GHSA-jqw5-w6h3-44g6) - [OSV: GHSA-jqw5-w6h3-44g6](https://osv.dev/vulnerability/GHSA-jqw5-w6h3-44g6) - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .