# Protected fields exposed via LiveQuery

Advisory record · `GHSA-crrq-vr9j-fxxh`

- **Identifiers:** `GHSA-crrq-vr9j-fxxh` · `BIT-parse-2022-31112` · `CVE-2022-31112`
- **State:** Confirmed
- **Severity:** CVSS 8.2 High
- **Critical:** No
- **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html) · [CWE-212](https://cwe.mitre.org/data/definitions/212.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md) · [CWE-212](https://agentprime.io/advisories/tag/cwe-212.md)
- **Published:** 6 Jul 2022
- **Updated:** 6 Dec 2023
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 6 Jul 2022, 19:52 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `parse-server` (npm): affected `<4.10.13 || >=5.0.0, <5.2.4`; fixed in `4.10.13`, `5.2.4`

## 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

- 8.2 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.013, the 71st percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 6 Jul 2022. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-crrq-vr9j-fxxh](https://github.com/advisories/GHSA-crrq-vr9j-fxxh)
- [OSV: GHSA-crrq-vr9j-fxxh](https://osv.dev/vulnerability/GHSA-crrq-vr9j-fxxh)
- <https://github.com/parse-community/parse-server/security/advisories/GHSA-crrq-vr9j-fxxh>
- <https://nvd.nist.gov/vuln/detail/CVE-2022-31112>
- <https://github.com/parse-community/parse-server/issues/8073>
- <https://github.com/parse-community/parse-server/pull/8074>
- <https://github.com/parse-community/parse-server/commit/054f3e6ab01d66a0dcfb77725af28eac1485b375>
- <https://github.com/parse-community/parse-server/commit/309f64ced8700321df056fb3cc97f15007a00df1>
- <https://github.com/parse-community/parse-server/commit/9fd4516cde5c742f9f29dd05468b4a43a85639a6>
- <https://github.com/parse-community/parse-server>
- <https://github.com/parse-community/parse-server/releases/tag/5.2.4>

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 (<https://api.agentprime.io/mcp>), 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: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-crrq-vr9j-fxxh>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-crrq-vr9j-fxxh/>. Everything for agents: <https://agentprime.io/llms.txt>.