CVE-2022-31112

HIGHNVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under NVD CVSS v3. EPSS exploit probability: 1.2%, top 34% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.2Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. In affected versions parse Server LiveQuery does not remove protected fields in classes, passing them to the client. The LiveQueryController now removes protected fields from the client response. Users are advised to upgrade. Users unable t upgrade should use Parse.Cloud.afterLiveQueryEvent to manually remove protected fields.

CVSS v3
8.2
EG Score
8.2(medium)
EG Risk
52(Track)
EG Risk 52/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity82% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
69%
KEV
Not listed

Published

June 30, 2022

Last Modified

November 21, 2024

Advisory Details (6)

Auto-updated Sep 8, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
github_pr

fix: protected fields exposed via LiveQuery (GHSA-crrq-vr9j-fxxh)

Fix merged in parse-community/parse-server PR #8074 on 2022-06-30 — awaiting tagged release

https://github.com/parse-community/parse-server/pull/8074
generic

fix: protected fields exposed via LiveQuery (GHSA-crrq-vr9j-fxxh) by mtrezza · Pull Request #8073 · parse-community/parse-server · GitHub

https://github.com/parse-community/parse-server/issues/8073
github_commit Patch Available

commit 9fd4516cde5c (parse-community/parse-server)

Patch available: parse-community/parse-server 9.9.1-alpha.8 (contains commit 9fd4516cde5c)

https://github.com/parse-community/parse-server/commit/9fd4516cde5c742f9f29dd05468b4a43a85639a6
github_commit Patch Available

commit 309f64ced870 (parse-community/parse-server)

Patch available: parse-community/parse-server 9.9.1-alpha.8 (contains commit 309f64ced870)

https://github.com/parse-community/parse-server/commit/309f64ced8700321df056fb3cc97f15007a00df1
github Patch Available

Protected fields exposed via LiveQuery · Advisory · parse-community/parse-server · GitHub

https://github.com/parse-community/parse-server/security/advisories/GHSA-crrq-vr9j-fxxh
github_release Patch Available

5.2.4

Patch available: parse-community/parse-server 5.2.4

https://github.com/parse-community/parse-server/releases/tag/5.2.4

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
parse-server—5.2.4—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 27× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 161 total refreshes for this CVE.

  1. 2026-09-18 19:24 UTCEPSS rescore
  2. 2026-09-16 14:05 UTCEPSS rescore
  3. 2026-09-15 03:06 UTCEPSS rescore
  4. 2026-09-13 16:44 UTCEPSS rescore
  5. 2026-09-12 14:57 UTCEPSS rescore
  6. 2026-09-11 14:49 UTCEPSS rescore
  7. 2026-09-11 09:33 UTCEPSS rescore
  8. 2026-09-08 21:57 UTCEPSS rescore
  9. 2026-09-07 15:58 UTCEPSS rescore
  10. 2026-09-06 13:45 UTCEPSS rescore
  11. 2026-09-05 15:25 UTCEPSS rescore
  12. 2026-09-05 10:18 UTCOSV refresh
  13. 2026-09-04 13:57 UTCEPSS rescore
  14. 2026-09-04 13:57 UTCEPSS rescore
  15. 2026-09-04 05:04 UTCEPSS rescore
  16. 2026-09-02 14:09 UTCEPSS rescore
  17. 2026-09-01 13:51 UTCEPSS rescore
  18. 2026-08-30 19:14 UTCEPSS rescore
  19. 2026-08-30 01:19 UTCEPSS rescore
  20. 2026-08-28 21:38 UTCEPSS rescore
  21. 2026-08-27 14:22 UTCEPSS rescore
  22. 2026-08-26 14:43 UTCEPSS rescore
  23. 2026-08-25 13:46 UTCEPSS rescore
  24. 2026-08-24 14:13 UTCEPSS rescore
  25. 2026-08-23 00:16 UTCEPSS rescore
Show 75 more
  1. 2026-08-21 23:46 UTCEPSS rescore
  2. 2026-08-20 22:52 UTCEPSS rescore
  3. 2026-08-19 17:01 UTCEPSS rescore
  4. 2026-08-18 20:40 UTCOSV refresh
  5. 2026-08-18 13:45 UTCEPSS rescore
  6. 2026-08-16 14:53 UTCEPSS rescore
  7. 2026-08-16 02:11 UTCEPSS rescore
  8. 2026-08-15 01:27 UTCEPSS rescore
  9. 2026-08-13 21:57 UTCEPSS rescore
  10. 2026-08-12 13:48 UTCEPSS rescore
  11. 2026-08-11 13:38 UTCEPSS rescore
  12. 2026-08-09 13:44 UTCEPSS rescore
  13. 2026-08-08 16:34 UTCEPSS rescore
  14. 2026-08-07 16:24 UTCEPSS rescore
  15. 2026-08-06 13:44 UTCEPSS rescore
  16. 2026-08-05 19:15 UTCEPSS rescore
  17. 2026-08-04 15:07 UTCEPSS rescore
  18. 2026-08-04 10:35 UTCEPSS rescore
  19. 2026-08-03 16:57 UTCOSV refresh
  20. 2026-08-03 10:33 UTCEPSS rescore
  21. 2026-08-02 02:24 UTCEPSS rescore
  22. 2026-08-01 04:13 UTCEPSS rescore
  23. 2026-07-30 16:25 UTCEPSS rescore
  24. 2026-07-30 01:28 UTCEPSS rescore
  25. 2026-07-28 15:33 UTCEPSS rescore
  26. 2026-07-26 14:52 UTCEPSS rescore
  27. 2026-07-25 14:15 UTCEPSS rescore
  28. 2026-07-24 14:15 UTCEPSS rescore
  29. 2026-07-24 14:15 UTCEPSS rescore
  30. 2026-07-23 14:16 UTCEPSS rescore
  31. 2026-07-23 14:16 UTCEPSS rescore
  32. 2026-07-23 02:11 UTCEG score recompute
  33. 2026-07-22 22:58 UTCEG score recompute
  34. 2026-07-22 14:06 UTCEPSS rescore
  35. 2026-07-22 14:06 UTCEPSS rescore
  36. 2026-07-21 15:22 UTCEPSS rescore
  37. 2026-07-21 15:22 UTCEPSS rescore
  38. 2026-07-20 17:05 UTCEPSS rescore
  39. 2026-07-19 02:27 UTCEPSS rescore
  40. 2026-07-19 02:27 UTCEPSS rescore
  41. 2026-07-18 10:03 UTCEPSS rescore
  42. 2026-07-18 10:02 UTCEPSS rescore
  43. 2026-07-17 04:54 UTCOSV refresh
  44. 2026-07-16 17:00 UTCEPSS rescore
  45. 2026-07-15 16:56 UTCEPSS rescore
  46. 2026-07-15 16:56 UTCEPSS rescore
  47. 2026-07-15 01:58 UTCEPSS rescore
  48. 2026-07-15 01:58 UTCEPSS rescore
  49. 2026-07-13 22:27 UTCEPSS rescore
  50. 2026-07-12 05:44 UTCEPSS rescore
  51. 2026-07-12 05:44 UTCEPSS rescore
  52. 2026-07-11 08:25 UTCEPSS rescore
  53. 2026-07-11 08:25 UTCEPSS rescore
  54. 2026-07-09 19:07 UTCEPSS rescore
  55. 2026-07-08 15:12 UTCEPSS rescore
  56. 2026-07-07 13:44 UTCEPSS rescore
  57. 2026-07-06 16:25 UTCEPSS rescore
  58. 2026-07-06 16:25 UTCEPSS rescore
  59. 2026-07-06 02:21 UTCEPSS rescore
  60. 2026-07-06 02:21 UTCEPSS rescore
  61. 2026-07-05 02:28 UTCEPSS rescore
  62. 2026-07-05 02:28 UTCEPSS rescore
  63. 2026-07-04 06:29 UTCEPSS rescore
  64. 2026-07-04 06:29 UTCEPSS rescore
  65. 2026-07-01 15:04 UTCEPSS rescore
  66. 2026-06-30 23:20 UTCEPSS rescore
  67. 2026-06-30 23:20 UTCEPSS rescore
  68. 2026-06-29 14:04 UTCEPSS rescore
  69. 2026-06-29 03:02 UTCOSV refresh
  70. 2026-06-28 14:06 UTCEPSS rescore
  71. 2026-06-28 04:54 UTCEPSS rescore
  72. 2026-06-27 03:07 UTCEPSS rescore
  73. 2026-06-25 13:48 UTCEPSS rescore
  74. 2026-06-25 13:48 UTCEPSS rescore
  75. 2026-06-24 14:03 UTCEPSS rescore

Frequently asked(5)

What is CVE-2022-31112?
CVE-2022-31112 is a high vulnerability published on June 30, 2022. Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. In affected versions parse Server LiveQuery does not remove protected fields in classes, passing them to the client. The LiveQueryController now removes protected fields from the client response.…
When was CVE-2022-31112 disclosed?
CVE-2022-31112 was first published in the National Vulnerability Database on June 30, 2022, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-31112 actively exploited?
CVE-2022-31112 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 30.8% of all scored CVEs.
What is the CVSS score of CVE-2022-31112?
CVE-2022-31112 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2022-31112?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-31112, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-31112

Explore →

Is Your Infrastructure Affected by CVE-2022-31112?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs