Advisory record · GHSA-vf7h-6246-hm43

The disqualify lead action may be executed without CSRF token check

CVSS 4.2 MediumEPSS 0.0031 · 24th percentile

Published by the GitHub Advisory Database at 19 Nov 2021, 20:18 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
oro/crmPackagist>=3.1.0, <4.1.17 || >=4.2.0, <4.2.74.1.17, 4.2.7
Identifiers
GHSA-vf7h-6246-hm43 · CVE-2021-39198 · PKSA-q9vg-cpjn-sk23
Weakness (CWE)
CWE-352
Published
19 Nov 2021
Updated
8 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The oro/crm package versions 3.1.0 up to 4.1.17 and 4.2.0 up to 4.2.7 are affected. A remote attacker can use a cross-site request forgery attack to disqualify any Lead. Upgrade to version 4.1.17 or 4.2.7. The source lists no workarounds.

Written 3 Nov 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

ScoreRatingCVSSVectorSource
4.2 Medium 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:L CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0031, the 24th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:25 UTC First seen by agentprime
  2. 31 Oct 2026, 14:25 UTC Confirmed by OSV

Sources

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.